How to monitor a Windows process' working set greater than 4GB?

Posted by Shoeless on Server Fault See other posts from Server Fault or by Shoeless
Published on 2012-07-10T19:04:56Z Indexed on 2012/07/10 21:18 UTC
Read the original article Hit count: 163

Apparently the .NET framework has a bug that prevents working set values above 2GB from accurately being determined. Between 2 and 4GB one can apply some xor-ing calculation to obtain the value, but there's no means of obtaining working set values greater than 4GB (using .Net or WMI)

What method can be used - preferably from a PowerShell script - to obtain an accurate measurement of a process' working set when the working set is greater than 4GB?

(some side details can be found in this StackOverflow question)

© Server Fault or respective owner

Related posts about windows-server-2008

Related posts about windows-server-2003