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 Direct connect
- 8.8.2 SSH access
- 8.8.3 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 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 CPU and wall times when profiling .NET applications
- 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 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
- 14 Memory profiling
- 14.1 Understanding garbage collection
- 14.2 Shallow and retained sizes
- 14.3 Object allocation profiling
- 14.4 GC roots view
- 14.5 Memory tab
- 14.5.1 Telemetry
- 14.5.2 Classes
- 14.5.3 Object explorer
- 14.5.4 Dominators - Biggest objects
- 14.5.5 Memory inspections
- 14.5.6 Group objects by category
- 14.5.6.1 Class
- 14.5.6.2 Class and namespace
- 14.5.6.3 Domain and module
- 14.5.6.4 Generation
- 14.5.6.5 Shallow size
- 14.5.7 Allocations
- 14.5.7.1 Call tree - All threads merged
- 14.5.7.2 Call tree - By thread
- 14.5.7.3 Flame graph
- 14.5.7.4 Hot spots by object count
- 14.5.7.5 Hot spots by object size
- 14.5.7.6 Method list
- 14.5.8 Method merged callees view
- 14.5.9 Method back traces view
- 14.5.10 Quick info view
- 14.5.11 Leak detection: working with paths
- 14.5.12 Merged paths
- 14.5.13 Class hierarchy
- 14.6 Useful actions
- 15 Garbage collection
- 16 Exception profiling
- 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
- 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