- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- 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
- Compiling probe classes
- Probe registration, activity modes
- Probe unregistration
- Monitoring method invocation events
- Data storage
- 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?
Probe unregistration
Registered probe can be unregistered in runtime. This means that all methods which have been instrumented with the probe's callbacks will be returned to their original state.
We strongly recommend to change the probe's activity mode to Off instead.
Probe unregistration is only possible using the profiler API:
invoke static method unregisterProbes() of class com.yourkit.probes.Probes:
public static void unregisterProbes(final String... probeClassNames);
public static void unregisterProbes(final Class... probeClasses);Examples
import com.yourkit.probes.*;
// ...
Probes.unregisterProbes(MyProbe.class);
Probes.unregisterProbes("com.foo.Probe1", "com.foo.Probe2");