Activity overview
Latest activity by m_peretz
My problem is that our target machine is a mchine with no virtual memory. Therefore private bytes is the right counter to use, it indicates exactly how many bytes are used by the process. The BLOG you sent me confirms this So what are these Private Bytes? This is memory allocated to the process that cannot be shared by other processes. It is probably the most useful single figure when you want to know “How much memory does my app use?†It still needs qualification. As we’ve seen, the Private Bytes may not all be in physical memory. If they are swapped to disk, and the user isn’t actively using the application, then they aren’t having much impact on other applications
It is the working set size that is misleasing.
so at the end, I am looking at huge private bytes count compare to the managed heap count, and with no way to understand why it is so high. / comments
My problem is that our target machine is a mchine with no virtual memory. Therefore private bytes is the right counter to use, it indicates exactly how many bytes are used by the process. The BLOG ...
The private bytes is performace counter under the process title. That counter is far greater then CLR Memory # of bytes in all heaps. / comments
The private bytes is performace counter under the process title. That counter is far greater then CLR Memory # of bytes in all heaps.
Private bytes vs bytes allocated by .NET heaps
We just got ANTS.NET to find out why our application is taking over 150M of private bytes. According to the profiler, only 20M of memory is used for all managed heaps. At that point, I am stuck won...