.NET Best Practice No: 1: Detecting High Memory consuming functions in .NET code

Introduction and Goal
Thanks a lot Mr. Peter Sollich
CLR Profiler to rescue
Features of CLR profiler
Do not user CLR on production and as a starting tool for performance evaluation
How can we run CLR profiler?
Issues faced by CLR profiler
The sample application we will profile
Using CLR profiler to profile our sample
That was a tough way any easy way
Simplifying results using comments
As said before do not get carried away with execution time
Conclusion.
Source code
Other Articles
My FAQ articles

Introduction and Goal

One of the important factors for performance degradation in .NET code is memory consumption. Many developers just concentrate on execution time to determine performance bottle necks in a .NET application. Only measuring execution time does not clearly give idea of where the performance issue resides. Ok, said and done one of the biggest task is to understand which function, assembly or class has consumed how much memory. In this tutorial we will see how we can find which functions consume how much memory. This article discusses the best practices involved using CLR profiler for studying memory allocation.

Please feel free to download my free 500 question and answer ebook which covers .NET , ASP.NET , SQL Server , WCF , WPF , WWF@ http://www.questpond.com .

Thanks a lot Mr. Peter Sollich

Let’s start this article by first thanking Peter Sollich who is the CLR Performance Architect to write such a detail help on CLR profiler. When you install CLR profiler do not forget to read the detail help document written by Peter Sollich.

Thanks a lot sir, if ever you visit my article let me know your inputs.

Read more: Codeproject

Posted via email from .NET Info