- 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
- Threads
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Events in user interface
- 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)
- 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?
Table API
To create a table, create instance of class com.yourkit.probes.Table.
You will need that instance to create rows, as well as to close table rows
for lasting events.
Table columns are described with instances of classes
com.yourkit.probes.IntColumn,
com.yourkit.probes.LongColumn,
com.yourkit.probes.StringColumn,
com.yourkit.probes.ForeignKeyColumn.
The column instances are passed as parameters to com.yourkit.probes.Table
constructor.
They are also used to set or modify values at specified row.
Please see Javadoc for detail.
Please also read about compiling probe classes.
Please find examples of the API usage in the built-in probes source code.