Page Comparison - First Look at Subsystems (v.11 vs v.12)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The first thing you see in dotTrace Performance Viewer is the Overview page. This page contains general performance information: the list of hotspots (calls with the highest own time), snapshot options, and more.

Starting dotTrace Performance 5.5, the page also contains the list of subsystems shown against the app's threads. This list contains subsystems from the Default profile – a set of subsystems that comes with dotTrace Performance out of the box. The Default profile includes all major .NET Framework subsystems, such as WinForms and WPF, Collections, LINQ etc.

As you can see, even before going outside of the defaults, subsystems help us understand main performance hot spots. For example, just a quick glance on the default profile shows that our app works with Collections a lot.
Let’s look at subsystems in the Default profile in more detail. To do this, we switch dotTrace Performance to the Threads Tree view.  

Note that subsystems are shown specifically for a call or thread selected in the call tree. Thus, if Main Thread is selected, dotTrace Performance Viewer shows the time consumed by a certain subsystem out of all calls performed by the app. For example, the WinForms subsystem has taken 1894 ms - this includes the time of all calls in the System.Windows.Forms assembly.
Subsystems are presented in two ways: