I have a couple of different tests, one is:
select VirtualSize from Win32_Process where caption='STORE.EXE'
It returns 280371200 - which I would assume is ~2.8gb of memory, however if I actually look on the server, it is using 2.1gb.
The second is:
select VirtualSize from Win32_Process where caption='beremote.exe'
That test returns 183822360, but the service is only using 698mb of memory.
Am I looking at the wrong thing?
WMI - strange replies
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Actually, VirtualSize is returned in bytes, so 280371200 bytes is ~ 267Mb, not 2.8gb. I suppose, you have compared this value with VMSize column in Task Manager, haven't you? In such case you have to use "PageFileUsage" counter. Quote from the Microsoft:
http://msdn2.microsoft.com/en-us/library/aa394372.aspx
--------------------------------------------------------
PageFileUsage - Amount of page file space that a process is using currently. This value is consistent with the VMSize value in TaskMgr.exe
VirtualSize - Current size of the virtual address space that a process is using, not the physical or virtual memory actually used by the process. Using virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and by using too much, the process might not be able to load libraries. This value is consistent with what you see in Perfmon.exe.
--------------------------------------------------------
BTW. If you want to check Memory usage that is consistent with MemUsage column in Task Manager, you have to use "WorkingSetSize" counter.
Regards,
Max
http://msdn2.microsoft.com/en-us/library/aa394372.aspx
--------------------------------------------------------
PageFileUsage - Amount of page file space that a process is using currently. This value is consistent with the VMSize value in TaskMgr.exe
VirtualSize - Current size of the virtual address space that a process is using, not the physical or virtual memory actually used by the process. Using virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and by using too much, the process might not be able to load libraries. This value is consistent with what you see in Perfmon.exe.
--------------------------------------------------------
BTW. If you want to check Memory usage that is consistent with MemUsage column in Task Manager, you have to use "WorkingSetSize" counter.
Regards,
Max