- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- Solving performance problems
- CPU profiling
- CPU usage estimation
- Sampling
- Asynchronous sampling
- Tracing
- Call counting
- CPU tab
- CPU usage telemetry
- Call tree - All threads merged
- Call tree - By thread
- Flame graph
- Hot spots
- Method list
- Java EE 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
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- 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 Java API
- Profiler HTTP API
- Command line tool to control profiling
- Settings
- FAQ: How to profile in my scenario?
Method back traces view
Method back traces shows where a particular method was called. CPU | Method Back Traces (Ctrl+Shift+M) menu action opens the view for the selected method.
For each method you will see execution time and number of invocations if available.
Actions
The following actions are available in the popup menu:
- CPU | Method Merged Callees (Ctrl+M) - shows the method's merged callees.
- CPU | Method Back Traces (Ctrl+Shift+M) - shows the method's back traces.
- Tools | Open in IDE (F7) - opens method declaration in IDE editor. See IDE integration.