Fully featured low overhead profiler for Java EE and Java SE platforms.
Monitoring and profiling solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.
- Running the profiler
- Running applications with the profiler
- Connect to profiled application
- Troubleshoot connection problems
- Solving performance problems
- CPU profiling
- Threads
- Deadlock detector
- Memory profiling
- Memory telemetry
- Memory snapshot
- Object allocation recording
- Shallow and retained sizes
- Memory views
- Memory inspections
- Comparing memory snapshots
- Support of HPROF format snapshots
- Values of primitive types
- Useful actions
- Set description language
- Garbage collection
- Monitor profiling
- Exception telemetry
- Probes: monitor events of various kinds
- 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 API
- Command line tool to control profiling
- FAQ: How to profile in my scenario?
Memory snapshot
A memory snapshot represents the memory state of the profiled application at the moment it was captured. It contains information about all loaded classes, about all existing objects, and about references between objects.
Snapshots can contain values of fields and arrays of primitive types (int, long, char etc.).
Read more.
Optionally, snapshot can contain information about object allocations.
Snapshot formats
You have an option to capture snapshot in YourKit Java Profiler format or via JVM built-in dumper:
Read more about HPROF snapshots.