Hi, that's half-correct. I am after the current value of the process working set size. However, Windows also offers the ability to set min/max limits on working sets, using the SetProcessWorkingSetSize (2000 and XP) or SetProcessWorkingSetSizeEx (only available in Server 2003 and Vista) APIs. This actively affects how the memory manager behaves when paging processes in/out of physical memory. For example, if you use the Ex version of the API to implement a max limit of 10MB on a process, an instance of that process attempting to use a working set of 15MB would result in the least-recently-used 5MB being written to pagefile. (the non-Ex API behaves slightly differently, although is essentially the same thing) I would like the smaller indicators to return the values of these limits.
If it's too much hassle to get into the API calls, then tips for how to incorporate multiple perfmon counters into a single gadget via powershell would be just as welcome.
Thanks for your help.