Performance profiling of .NET code

The goal of performance profiling is finding a cause of performance problems in an application. This includes, for example, a straightforward "what is the slowest method?" analysis, as well as more complicated analysis of performance bottlenecks related to CPU starvation, blocking garbage collection, disk I/O, and other issues.

JetBrains Rider integrates with the dotTrace profiler to provide performance profiling of .NET applications. You can use the profiler via the dotTrace Profiler tool window.

Limitations

Note that not all dotTrace features are yet available in JetBrains Rider. Thus, the integrated profiler provides only two views for analyzing snapshots: Call Tree and Top Methods. To get the entire feature set, you should open profiling snapshots in the standalone version of dotTrace (Windows only).

Installation and licensing

dotTrace is provided as a bundled plugin for Rider, and installed along with Rider automatically with no additional actions needed. If you want to disable dotTrace, you can do this via Rider's Plugins settings.

Note that dotTrace is available in Rider only for the owners of dotUltimate or All Products Pack subscriptions.

Supported operating systems and frameworks

	Windows	macOS \| Linux
Native	Available in: JetBrains Rider, Visual Studio, standalone, console tool Supported profiling types: Timeline.
.NET Framework 1.0 – 4.8	Available in: JetBrains Rider, Visual Studio, standalone, console tool Supported profiling types: Timeline, Sampling, Tracing, Line-by-Line. Notes: You can attach only to .NET Framework 4.0 or later processes.
.NET Core 1.0 – 3.1 .NET 5 – 6	Available in: JetBrains Rider, Visual Studio, standalone, console tool Supported profiling types: Timeline, Sampling, Tracing, Line-by-Line. Notes: You can attach only to .NET Core 3.0 or later processes.	Available in: JetBrains Rider, console tool Supported profiling types: Timeline, Sampling, Tracing. Notes: Because of some limitations of .NET Core, there may be some issues with profiling projects that target .NET Core 3.0 or earlier. In some cases, the profiled application may hang or crash. Projects targeting .NET Core 3.1 can be profiled without any issues. Attaching to running .NET Core processes is possible: On Linux: only for .NET Core 3.0 or later. On macOS: only for .NET 5 or later.
Mono 5.10 and later	Available in: JetBrains Rider, Visual Studio, standalone, console tool Supported profiling types: Timeline.	Available in: JetBrains Rider, console tool Supported profiling types: Timeline. Notes: Only 64-bit processes can be profiled. Attaching to running Mono processes is not possible.
Mono Unity 2018.3 and later	Available in: JetBrains Rider, Visual Studio, standalone, console tool Supported profiling types: Timeline.	Available in: JetBrains Rider, console tool Supported profiling types: Timeline. Notes: Attaching to running Unity processes is not possible.

What can you profile with Rider

Last modified: 07 April 2022