Process explorer

Can someone explain the difference between private bytes and Working set?

Thanks!

 

All I know is that Working Set is equivalent to Mem Usage in Task Manager and Private Bytes is equivalent to Task Manager's Virtual Memory.

If you want technical definitions:

 

So working set is actual ram usage

 

i just editted my post, check it again.

 

Hello

Private memory is RAM used (on chips).

Working set is the part of swap file currently used (not maximum available).

Cheers.

 

From my limited understanding, private bytes are the current number of bytes a process has allocated that cannot be shared with other processes—in other words, how much non-shared memory the process is using. This memory is more important than shared memory when multiple processes execute on a machine and are the primary counter for measuring memory leaks and overall memory usage. This corresponds to the VM Size column in Task Manager. Some of this memory could be swapped to disk at some point and not affecting other apps in RAM. Still, this is the amount of memory the app uses in a non-shared way and is important to minimize as if it grows appreciably over time it represents a memory leak.

Mem Usage in Task Manager refers to the number of pages of virtual memory committed to a given process, both shared and private - also called the working set. This is what is being kept in RAM at the time it is measured. This will fluctuate over time as compared to VM Size which shouldn't.

You can use perfmon to measure private bytes and working set and graph out to see application memory performance.

 

Private bytes= page file used
Working set= ram used

It,s my understanding. I think you reversed it.

 

Hi.

Yes, I stand corrected. I've done some reading, and you are right. I was a bit quick again... The working set is RAM...

 

Wow, this is confusing i think..

SO working set = actual ram used (so if I have a 256k of ram, and working set says 56k, I have 200 left), easy as that?