- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Telemetry
- Thread states
- Frozen threads
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
Thread telemetry
Thread telemetry contains subset of telemetry charts, focusing specifically on thread-related performance metrics. It provides insights into key aspects of thread activity, such as the number of running threads, threads started per second, and other thread-specific statistics.
Toolbar
-
:
Zoom in and out to quickly change the range of visible data.
-
:
Show "empty" charts, i.e. the charts that have only zero values.
-
:
Smooth out short-term fluctuations on graphs.
This is useful for visualizing of fast-changing data.
-
:
Control auto-scrolling behavior of telemetry charts.
When toggled, the graphs will be automatically scrolled to the right
when new data arrives.
Working with telemetry charts
Clicking on chart: Clicking on a chart reveals the call stacks of the .NET threads running at that specific moment, providing a snapshot of the application's state.
Selecting the time interval: Analyzing performance over a time span is equally straightforward. By selecting a range within the telemetry data, profiler builds an estimated call tree and computes the CPU usage for that interval. This can be invaluable for pinpointing performance bottlenecks or understanding the behavior of the application during periods of high load.