Analyze Profiling Results
The next step after taking a profiling snapshot is analyzing it in dotTrace Viewer. Note that dotTrace is also available in JetBrains Rider and Visual Studio. Both integrated viewers are almost identical to the standalone dotTrace Viewer but have some limitations. For the details about the viewer in JetBrains Rider, refer to the Rider documentation. For the details about the viewer in Visual Studio, refer to the section below.
Get Started
If you are new to dotTrace Viewer, start with the dotTrace Viewer Concepts section. In addition, we strongly recommend that you read Find the Cause of a UI Freeze.
Reference
The following sections contain details about viewer filters and diagrams and can be used as a reference to the dotTrace Viewer user interface:
dotTrace Viewer Integrated into Visual Studio
If, when installing dotTrace you have chosen the Visual Studio Integration option, your Visual Studio has a built-in dotTrace Viewer. This viewer is represented with the Performance Profiler tool window, and in terms of functionality it is almost identical to the standalone dotTrace Viewer. The list of collected snapshots is synced between the viewers.
Pros and cons of using the integrated viewer:
More seamless experience. As analysis is performed in Visual Studio, there is no need to switch between the source code and the profiler.
Navigation from call tree to the source code and vice versa.*
You can navigate from a particular method in Call Tree (in the profiling results) right to its declaration, as well as from the method declaration in the code to its occurrence in Call Tree.
Analyzing big amounts of profiling data in Visual Studio may be inconvenient due to the lack of space on the screen.