- 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?
This view shows events in a particular table. If the table has dependent tables, they are presented as dependent views:
Number of events in table is shown in the title.
Table columns. Grouping and visibility.
Events can be presented as a plain list, as well as grouped by arbitrary column(s).
For each group you can see sum, minimum and maximum values for numeric columns.
In addition to own table columns, you can also get statistics on associated rows of dependent columns: the number of the rows, as well as sum, minimum and maximum values of the dependent table's metrics.
Also, you can hide columns to give more space for others.
All this can be configured via "Configure columns and groping" action:
Navigation between views
To open selected event(s) in another view, use corresponding popup menu items. Read more...