Analyzing Timeline Profiling Results in Visual Studio
Since dotTrace 10, you can analyze timeline profiling results right in Visual Studio (as an alternative to the standalone Timeline Viewer). This is done with the help of a special Timeline Viewer version integrated in Visual Studio. This viewer is represented with the Performance Profiler window and in terms of functionality it is almost identical with the standalone Timeline Viewer.
Pros 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.
Differences between the Integrated and Standalone Timeline Viewer
- Threads Diagram is not available in the integrated viewer, therefore, it is not possible to view threads timeline. Nevertheless, thread selection is available via the Threads filter with the only limitation - the filter does not support multiple thread selection.
- Filter grouping is different. There are no Interval Filters and Analysis Subject groups in the integrated viewer. Some of these filters are grouped under Events, while others are made standalone.
- Different shortcuts in Top Methods and Call Tree: In the integrated viewer, double click or Enter on a method navigates you directly to the method declaration.
If you are new to timeline profiling, start with the Timeline Viewer Concepts section.
In addition, we strongly recommend that you read the Getting Started with Timeline Profiling and Improving App Performance with Timeline Profiling. Memory Traffic tutorials.
If you are already acquainted with the timeline profiling, proceed to the Performance Profiler Concepts section. It provides details on the user interface of the integrated viewer.
As Performance Profiler and standalone Timeline Viewer provide almost the same functionality, you can use the corresponding sections dedicated to the standalone viewer as a reference for the integrated one.