Memory Profiling
dancaron
Posts: 2
I am profiling the DotNetNuke application portal to profile the memory utilization in an upcoming release of DotNetNuke. According to Ants Profiler, our app is consuming about 3 megs of memory.
Many users of our portal software report memory consumption of 50 megs, 100 megs, 300 megs. They are measuring this in Task Manager.
Can someone please explain the differences we are seeing? Obviously the task manager is taking other components into account...perhaps some IIS resources are being rolled up into the numbers that it reports. The difference, though, is large enough to necessitate some detailed explanation.
This is important because in the hosting environment, many hosts will set machine.config to recycle web apps after they consume a pre-defined amount of memory...so for instance, it will recycle the worker process once an application reaches 100 megs of memory. We need to understand how this measurement relates to what I am seeing in Ants Profiler. The two measurements seem to be comparing apples & oranges.
Thanks,
Dan
Many users of our portal software report memory consumption of 50 megs, 100 megs, 300 megs. They are measuring this in Task Manager.
Can someone please explain the differences we are seeing? Obviously the task manager is taking other components into account...perhaps some IIS resources are being rolled up into the numbers that it reports. The difference, though, is large enough to necessitate some detailed explanation.
This is important because in the hosting environment, many hosts will set machine.config to recycle web apps after they consume a pre-defined amount of memory...so for instance, it will recycle the worker process once an application reaches 100 megs of memory. We need to understand how this measurement relates to what I am seeing in Ants Profiler. The two measurements seem to be comparing apples & oranges.
Thanks,
Dan
This discussion has been closed.
