Which memory counter best describes the actual physical memory utilized by an application and is there a threshold value in perfmon for memory?

by McNeill Dsilva   Last Updated August 13, 2019 22:01 PM

I'm running some performance tests on client machine to capture the Response time and resource utilization by applications, which is the memory counter that i need to look at to get the right physical memory that is utilized by the application? Private bytes/Working set/Working set-Private or should I be looking at? Right now I use Perfmon to capture the Process CPU and memory, the application I'm testing is leaking memory, during the test, the private byte and Working set counter gets maxed at around 4GB and wont capture data beyond 4GB. I'm running this test on Windows 7 and Windows 10 machines and both give me the same result. I use splunk to capture the same data(my machines are live feeding all perfmon data into splunk), there I see the same counters reaching 12-14 GB(physical memory available on the machine is 16 GB). Need advise on why the perfmon data I capture through a powershell script hits the 4 GB threshold and am I looking at the right memory counters to capture the actual physical memory used.

Related Questions

Updated August 09, 2017 19:01 PM

Updated March 31, 2017 20:01 PM

Updated April 10, 2017 13:01 PM

Updated March 31, 2018 06:01 AM

Updated May 28, 2016 08:00 AM