How to monitor total memory occupied by a running project?

[vgbraymond]

Hi Matt,

  I am trying to understand the numbers..

  I run the VI you gave me on the PC that's now running a project for around 3 days already. I think (point out if I am wrong) what I should do is to run your VI by this project, then I will be able to obtain the information of the whole Labview.exe (in other words, i don't have to integrate your VI into my project), am I correct?

  Then I have the attached capture.

  I checked the definition of working set here. Looks like it's the memory the Labview.exe is using. My interpretation would be... LV is now using 105MB (which is consistent with task manager) of memory while it once used as much as 605MB.

  For Paged pool, Non-paged pool and page file, I am still trying to understand the difference among them and difference between each of them and working set... I cannot find any linkage between those numbers and numbers I saw in the task manager. I am checking out this page for information but I am having a hard time understanding it.. I am not a computer science guys... However I am trying hard!

  Looks like I can make some plot with "Working set size".

Raymond

[vgbraymond]

Hi Matt,

  That would be out-of-topic if I ask this question, but it's important for me to understand the numbers so I can really use them...

  I read a few articles and I get the following interpretation.

  Working set is roughly what we always talk about memory in bytes that are being used.

  Paged pool and non paged pool is a pool of address of memory. The RAM is mainly divided into two parts -- address pools and storage area. The paged pool contains address that can be paged out to harddisk while the non paged pool cannot. The adv. of non paged pool is that data in it won't be moved out of the RAM so program can access it quickly without waiting it from being moved back to the RAM.

  Pagefile is the total amount of harddisk space allocated to map to the paged pool. 

  Pagefault is the number of time the system page-in data from harddisk to memory.

So in the table, 

  Working set is what I am of concern. Pagefile and Peakpagefile ain't only containing information of Labview.exe, but the whole system, I made this guess because their numbers are greater than working set and peakworkingset respectively.

  For paged pool and unpaged pool, since they are addresses for memory (working set), they increase accordingly when working set increases.

  And for a safe program, the working set and its fluctration should remains at a level.

Am I correct?

Thanks,

Raymond

[vgbraymond]

Oh! I think the page file is still only relevant to the Labview.exe that's the system allocation of harddisk memory for the paged memory. It's always greater than working set so there is always spare space for more data...

[myle00]

I'm no expert on this and some of the variables are a bit too vague, but as far as I know you're right about the definitions of these things. And the main thing to look at is the working set. However, you are not right that the Pagefile refers to system usage because they all refer to LabVIEW's usage.

[vgbraymond]

Thanks Matt 🙂 You really helped me a lot!