DotTrace lets you spot problem portions of code with great ease and accuracy. Once all major bottlenecks are located, you can start eliminating these bottlenecks.


After you apply certain optimization effort, it would be nice to compare the performance of your application before and after the optimization.

Usually, when profiling applications, you have to analyze the call tree. This part of the job is most tedious: digging through the endless sequences of nodes distracts you from focusing on real problem areas. With dotTrace’s smart navigation, this task becomes much easier.

We’ve released several short flash movies demonstrating how to profile using dotTrace. They are available right now in the dotTrace Docs and Demos section.
For quicker access, here is some short info about each movie and a quick link:
Performance profiling

Shows how to profile perfomance, locate performance bottlenecks, and use the automatic snapshot comparison feature. Illustrates working […]

dotTrace 2.0 offers two different ways to profile memory. Each of them is useful for a particular type of profiling tasks.

To analyze profiling data efficiently, you need to focus on the subsystems of your program.

Get started with optimizing your application’s memory by using dotTrace

dotTrace Profiler 2.0 will offer easy handling of massive class library calls by collapsing filtered calls