2

The windows Resource Monitor shows the memory usage of my app (debug running in visual studio) in the following figure:

enter image description here

However, the Diagnostic Tools shows the memory graph like:

enter image description here

The Commit size is

The Amount of virtual memory reserved by the operating system for the process in KB.

Does this mean all memory allocated in my app?

And the Private size in Resource Monitor is much less than it in the Diagnostic Tools, is the Private in the Resource Monitor doesn't count the pages that are swapped out into disk? So the Private + Shareable = Working Set.

Even the Process Memory in the graph is different from the Heap Size in the Diagnostic Tools, apart from Heap Size is there any Stack Size that will be 100M large? enter image description here

Joey.Z
  • 4,492
  • 4
  • 38
  • 63
  • It's important to remember that "virtual memory" is not synonymous with "swap file". https://en.wikipedia.org/wiki/Virtual_memory – xaxxon Oct 20 '16 at 05:23
  • @xaxxon Yes, but isn't the size of swap file and physical usage add up to the size of virtual memory used by a executable – Joey.Z Oct 20 '16 at 05:33
  • My incomplete understanding is that the "commit" is a reserved chunk that is bigger than what is actually used and is expanded as your app approaches the currently reserved amount. – xaxxon Oct 20 '16 at 05:38
  • I can't tell what the question is here. – user3344003 Oct 29 '16 at 19:39
  • I suggest watching https://www.youtube.com/watch?v=AjTl53I_qzY (and the 2nd part) as potential refresher and source of insight on why tools may report different numbers for what they would name similarly, etc. – mlvljr Oct 30 '16 at 01:00

0 Answers0