- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Running applications with the profiler
- Connect to profiled application
- Troubleshoot connection problems
- Solving performance problems
- CPU profiling
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Events in user interface
- Event Table
- Event Timeline
- Event Call Tree
- Event stack traces
- Navigation between views
- Events in range
- Event inspections
- Built-in probes
- Probe classes
- Monitoring method invocation events
- Data storage
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- IDE integration
- Time measurement (CPU time, wall time)
- 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
- FAQ: How to profile in my scenario?
Events in user interface
The probes and their results are shown in tab "Events".
The tab is available when the profiler is connected to profiled application, as well as browsing saved snapshot.
Some functionality is available for a saved snapshot only.
The view consists of two parts:
1. Table selector
Shows all available tables as a tree: dependent tables are show as nested nodes of their primary tables.
Selected table is shown in Event Table (see below).
2. The views
- Event Table shows events in the table, which is selected in the table selector (1).
- Event Timeline shows event sequence in a table form. Use the table selector (1) to specify which events to include.
- Event Call Tree shows events distributed by stack trace. Use the table selector (1) to specify which events to include.
Navigation between the views
To open selected event(s) in another view, use corresponding popup menu items. Read more...