- 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
- com.yourkit.probes.builtin.Threads
- Class loading probe
- com.yourkit.probes.builtin.AwtEvents
- 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?
Class loading probe
Description
Probe records class load and unload events.
Results are available in the probes UI in table "Class Loading".
You can quickly access them from "Classes" telemetry clicking link "Detail...":
Enabling/disabling the probe via startup options
Use probe name com.yourkit.probes.builtin.ClassLoading
in corresponding startup options,
e.g. probe_off=com.yourkit.probes.builtin.ClassLoading disables the class loading probe.