Web 2.0 ASP.NET

I have been using DotTrace for a while now and have always found it invaluable when digging into an application to find performance bottlenecks and memory leaks. Before DotTrace it was a real pain trying to lock down these problems (often so obscure that the Hubble space telescope could find it difficult to see!).

What DotTrace does is to take a snapshot of an application, while it is running, from a performance/memory usage perspective and then provide you with several ways of digging into your code and highlighting potential hotspots or problematic areas.



This is of course galaxies better than any kind of debugging, tracing or simply just reading the code! Finding a memory leak in an application without a tool is just like looking for the proverbial needle in a haystack and often times, having sifted through the billion lines of code, you always find the problem in your back pocket far far away from any place you would have thought to look.

With this release DotTrace has now split into 2 logical versions DotTrace 4.0 Performance Profiler and DotTrace 3.5 Memory Profiler, I will be writing more detailed posts soon on both. My initial reaction is that both are performing better than the previous version and, more importantly, the new UI makes it even easier to see issues immediately.

You can get a Trial Versions of DotTrace 4.0 Performance Profiler and DotTrace 3.5 Memory Profiler Here:

DotTrace 4.0 Performance Profiler

DotTrace 3.5 Memory Profiler