- 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
- 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?
What-if: an ability to ignore particular methods or focus on particular methods only
"What-if" feature helps you to analyze CPU profiling results by ignoring particular methods or focusing on particular methods only.
This feature requires capturing a snapshot. It is not available in live views.
In views with CPU profiling results (call tree, method list, hot spots), use menu actions (available as popup menu and in main menu):
- CPU | Exclude Method - opens a new tab with CPU results modified such that all calls to the selected method are ignored.
- CPU | Exclude Subtree - opens a new tab with CPU results modified such that the selected method call is ignored.
- CPU | Focus on Method - opens a new tab with CPU results modified such that all methods except for the selected method are ignored. Methods, which called the selected method are shown too, but their times only include time spent in the selected method.
- CPU | Focus on Subtree - opens a new tab with CPU results modified such that they include only selected method call. Parent method times only include time spent in the selected subtree.
