Question on Profiler

[Bhargavan]

Hi,
I am running a .Net windows application. When I check the memory usuage of
that application in the windows task manager, it shows around 66MB. But when
I check the memory usuage using .NET memory profiler (a third party tool) it
shows only 4MB. Anybody have any idea why there is such a high discrepency?
Thanks,
Bhargavan

[Willy Denoyette [MVP]]

"Bhargavan" <bh********@yahoo.co.in> wrote in message
news:Oe**************@TK2MSFTNGP12.phx.gbl...

Hi,
I am running a .Net windows application. When I check the memory usuage of
that application in the windows task manager, it shows around 66MB. But
when I check the memory usuage using .NET memory profiler (a third party
tool) it shows only 4MB. Anybody have any idea why there is such a high
discrepency?
Thanks,
Bhargavan

Your .NET profiler only shows the amount used by the managed heap, taskman
shows the Working set op your process, that is the size of all pages
actually mapped into your process space,that is:
native code of the CLR, C runtime, system loaded DLL's unmanaged heap space,
framework native code, managed assemblies loaded, JIT compiled code, managed
heap etc....

So what you are looking at in the profiler is only a small part of what's
actually mapped into your process space.

Willy.