Here is why you must look for VS2012 memory Profiling. Apparently Tier Interaction VS2010 has done good job however memory profiling was not that profound as it is in VS2012. For more information you can check out http://blogs.msdn.com/b/dotnet/archive/2013/04/04/net-memory-allocation-profiling-with-visual-studio-2012.aspx
The purpose of this diagnostic tool is to find two essential problems in given system.
1. Memory Leaks- The unrooted memory referenes are freed by GC. Sometimes it may happen there are memory that are no longer used and still have rooted references are still not clear or handles such cases can be figured out through this tool.
2. Unwanted Allocation: Rule- More memory allocated more frequent GC happens.More objects survice GC collects, More GC operations performed to check null object references. Unwanted allocations by program may lead to unneccessary GC operations which latter adds up to the performance of the applications.
One can also look at Red Ant Profiler tool and Perf
The purpose of this diagnostic tool is to find two essential problems in given system.
1. Memory Leaks- The unrooted memory referenes are freed by GC. Sometimes it may happen there are memory that are no longer used and still have rooted references are still not clear or handles such cases can be figured out through this tool.
2. Unwanted Allocation: Rule- More memory allocated more frequent GC happens.More objects survice GC collects, More GC operations performed to check null object references. Unwanted allocations by program may lead to unneccessary GC operations which latter adds up to the performance of the applications.
One can also look at Red Ant Profiler tool and Perf
No comments :
Post a Comment