Why is Process.WorkingSet > Process.MaxWorkingSet?

问题

Idle curiosity...

I'm looking at some of the properties of the current process:

using(Process p = Process.GetCurrentProcess())
{
    // Inspect properties
    // p.MaxWorkingSet = 1,413,120
    // p.MinWorkingSet = 204,800
    // p.WorkingSet = 54,140,928
    // p.WorkingSet64 = 54,140,928
}

From my reading of the documentation, these properties are all related to the working set size in bytes, hence I was expecting to see:

MinWorkingSet <= WorkingSet <= MaxWorkingSet

This is not the case, can anyone explain why?

回答1:

MaxWorkingSet and MinWorkingSet are the values returned by the Win32 API GetProcessWorkingSetSize. These are limits used by the virtual manager that will be enforced when the memory is in short supply. As long as enough memory is available, the current working set size is allowed to grow larger than the value in MaxWorkingSet.

回答2:

While the MSDN is not really helpful in this case, a small investigation with the Process Explorer on the other hand revealed that the values for Private Memory/MaxWorkingSet and Shared Memory/WorkingSet do nearly exactly match.

Which makes me believe (yes, I do lack hard evidence) that the MaxWorkingSet does display the private memory while the WorkingSet64 does display the complete memory, including shared one.

_{I know what the MSDN says...and I don't care, I see something different in the Process Explorer.}

来源：https://stackoverflow.com/questions/7387055/why-is-process-workingset-process-maxworkingset