Currently "Working Set (MB)" is exposed via dotnet counters, which is totally fine. However, to have a full picture, wouldn't it be good to expose also "Private Bytes"?

Advantages:

• memory leaks awareness - we could look at both RAM usage and RAM + swap/page usage. If there is some strange memory leak, we may notice it by constant growth of committed memory (like page file(s) growth). I know, most "leaks" will be covered by GC Heap Size (MB) or # of Assemblies Loaded, but exposing private bytes seems to be a perfect counterpart to the existing one
• better picture of memory utilization - in various environments paging may be extensively influenced by other processes and looking only at Working Set may be misleading (sudden drops of WS in case of memory pressure etc.)

Disadvantages:

• overhead? I see how Environment.WorkingSet is implemented on Unix and this is how probably "private bytes" would be implemented too.