- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- IDE integration
- Profile .NET executable
- Profile ASP.NET application IIS
- Profile all .NET processes that will start
- Attach profiler to a running application
- Profile remote applications
- Profiling in Docker container
- Manually enable profiling of local applications
- Startup options
- Connect to profiled application
- Profiling troubleshooting
- Profiling overhead: how to reduce or avoid
- Capturing snapshots
- Solving performance problems
- CPU profiling
- Threads
- Memory profiling
- Garbage collection
- Exception profiling
- Probes: monitor higher level events
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Time measurement (CPU time, wall time)
- Filters
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler API
- Profiler HTTP API
- Command line tool to control profiling
- Settings
Start profiling
You have different options to start profiling of your application:
-
Profiler has seamless integration with Visual Studio and Rider. After installing the plugin, you will be able to profile applications directly from IDE.
-
Start and profile .NET executable from the profiler UI.
-
There is an option to profile all .NET processes. Use it for profiling of applications that start indirectly: services, spawned processes, etc.
-
Attach profiler to a running application.
-
Profiling can be done remotely when applications run on another computer.
- Manually enable profiling of your application.