Have you ever been in a situation or place where the first thing that flashes your mind is "It’s a déjà vu?" According to definition, déjà vu is an internal sense of a person who suddenly feels that he/she has already experienced the present noteworthy situation at some point in the past.
What about having déjà vus when developing and profiling your dot.net applications? I have been looking for information these days for the next conference titled "OOP Software meets Business", taking place in Germany and dealing with the performance of dot.net applications in relation to dot.net profilers. Recently, I came across the article “Tuning .NET Application Performance” from the msdn, and all of a sudden realized that, although written in May 2004, it demonstrated to me that many things have not changed much since then.
What caught my attention was the section "Performance Tuning Process" which states almost exactly what I wanted to say at the conference, of course, with different words.
If you want to eliminate bottlenecks in your dot.net applications you need to be iterative. However, being iterative is a time-consuming task that not all of us can afford due to the usual set cumpolsory project milestones (deadlines).
If you take a close look to the activities in Section 2 and 3 of the article, that’s where I always say our SpeedTrace dot.net profiler can be used with best results. First, look at "Collect Data"; it is said that we need to simulate load and capture metrics — excellent — our dot.net profiler will record your information to help you later with the activity in Section 3, "Analyse Results". That is where you identify performance issues and bottlenecks. How? — By using our dot.net profiler, of course.
However, we have not yet finished at this point, since the rest of the activities, "Configure", and "Test and Measure", need to undergo tuning in order to re-iterate the whole cycle.
So you can see that our SpeedTrace dot.net profiler will accompany you systematically during your whole dot.net development process.
The next time you start a new dot.net project, don’t forget to purchase your SpeedTrace toolkit so you can streamline your development and application with the right guidelines by using a really good dot.net profiler right from the outset. You won’t regret it!
