YourKit .NET Profiler help

1 System requirements
2 Profiler architecture
3 Profiler installation
4 Uninstall profiler
5 Running the profiler
6 Profiler activation
7 Welcome screen
8 Start profiling
- 8.1 IDE integration
- - 8.1.1 Visual Studio
  - 8.1.2 Rider
- 8.2 Profile .NET executable
- 8.3 Profile ASP.NET application in IIS
- 8.4 Profile ASP.NET web app on Azure App Service on Linux
- 8.5 Profile ASP.NET web app on Azure App Service on Windows
- 8.6 Profile all .NET processes that will start
- 8.7 Attach profiler to a running application
- 8.8 Profile remote applications
- - 8.8.1 AWS SSM
  - 8.8.2 Direct connect
  - 8.8.3 SSH access
  - 8.8.4 Connection broker
- 8.9 Profiling in Docker container
- - 8.9.1 Profiling in Docker container using port forwarding
  - 8.9.2 Profiling in Docker container using YourKit Connection Broker
- 8.10 Manually enable profiling of local applications
- 8.11 Agent startup options
- 8.12 Connect to profiled application
9 Profiling overhead
10 Snapshots
- 10.1 Snapshot directory
- 10.2 Snapshot annotation
- 10.3 Performance snapshot
- 10.4 Comparing performance snapshots
- 10.5 Memory snapshot
- 10.6 Comparing memory snapshots
11 Solving performance problems
- 11.1 Performance bottlenecks
- 11.2 Optimizing memory usage
- 11.3 Memory leaks
- 11.4 Excessive garbage allocation
12 CPU profiling
- 12.1 Wall time and CPU time
- 12.2 CPU profiling modes
- 12.3 CPU usage estimation
- 12.4 CPU sampling
- 12.5 CPU sampling settings
- 12.6 CPU tracing
- 12.7 CPU tracing settings
- 12.8 CPU tab
- - 12.8.1 Telemetry
  - 12.8.2 Call tree - All threads merged
  - 12.8.3 Call tree - By thread
  - 12.8.4 Flame graph
  - 12.8.5 CPU hot spots
  - 12.8.6 Method list
  - 12.8.7 Web and database profiling results
  - 12.8.8 Callee list view
  - 12.8.9 Method merged callees view
  - 12.8.10 Method back traces view
- 12.9 What-if: an ability to ignore particular methods or focus on particular methods only
13 Thread profiling
- 13.1 Telemetry
- 13.2 Thread states
- 13.3 Frozen threads
14 Object allocation profiling
- 14.1 Telemetry
- 14.2 Class
- 14.3 Allocation tree - All threads merged
- 14.4 Allocation tree - By thread
- 14.5 Flame graph
- 14.6 Hot spots by object count
- 14.7 Hot spots by object size
- 14.8 Method list
- 14.9 Method merged callees
- 14.10 Method back traces
15 Memory profiling
- 15.1 Understanding garbage collection
- 15.2 Shallow and retained sizes
- 15.3 GC roots view
- 15.4 Memory tab
- - 15.4.1 Telemetry
  - 15.4.2 Classes
  - 15.4.3 Object explorer
  - 15.4.4 Dominators - Biggest objects
  - 15.4.5 Memory inspections
  - 15.4.6 Group objects by category
  - - 15.4.6.1 Class
    - 15.4.6.2 Class and namespace
    - 15.4.6.3 Domain and module
    - 15.4.6.4 Generation
    - 15.4.6.5 Shallow size
    - 15.4.6.6 Object ages
  - 15.4.7 Quick info view
  - 15.4.8 Leak detection: working with paths
  - 15.4.9 Merged paths
  - 15.4.10 Class hierarchy
- 15.5 Useful actions
16 Exception profiling
- 16.1 Telemetry
- 16.2 Class
- 16.3 Exception tree - All threads merged
- 16.4 Exception tree - By thread
- 16.5 Flame graph
17 Telemetry
18 Probes: monitor higher level events
- 18.1 Enabling probes, probe activity modes
- 18.2 Events in user interface
- - 18.2.1 Event table
  - 18.2.2 Event timeline
  - 18.2.3 Event call tree
  - 18.2.4 Event stack traces
  - 18.2.5 Navigation between views
  - 18.2.6 Events in range
- 18.3 Event inspections
19 Inspections: automatic recognition of typical problems
20 Automatically trigger actions on event
- 20.1 Automatically capture snapshot on high memory usage
- 20.2 Capture snapshots periodically
21 Automatic deobfuscation
22 Summary, automatic deobfuscation
23 Filters
24 Profiler command line
25 Command line tool to control profiling
26 Export of profiling results to external formats
27 Profiler .NET API
28 Profiler HTTP API
29 Settings
- 29.1 Proxy
30 Troubleshooting