- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- Capturing snapshots
- Solving performance problems
- CPU profiling
- CPU usage estimation
- Sampling
- Tracing
- CPU tab
- CPU usage telemetry
- Call tree - All threads merged
- Call tree - By thread
- Flame graph
- Hot spots
- Method list
- Web and database profiling results
- Callee list view
- Method merged callees view
- Method back traces view
- What-if: an ability to ignore particular methods or focus on particular methods only
- Comparing performance snapshots
- Sampling settings
- Tracing settings
- 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
Web and database profiling results
You can profile applications in high-level terms like SQL statements and URLs. For each web and database call CPU time and invocation count are reported. These results are available in a captured snapshot and not available in "live" mode, when profiler is connected to the profiled application.
High-level results depends on corresponding probes whose activity mode is Auto by default, which means they are active only while CPU profiling is running.
Note, that high-level profiling requires bytecode instrumentation and adds some overhead to the running application. For detailed information, see Profiling overhead: how to reduce or avoid.
Database
Database section shows requests and their invocation method back traces. You can see the requests as a plain list, or you can group them by type.
Supported database types:
- Cassandra
- MongoDB
- SQL
Web
Shows list a of URLs that correspond to ASP.NET calls, and merged callees for all methods invoked with these URLs.
Actions
Lines can be copied by using File | Copy (Ctrl + C):