YourKit, LLC has announced the general availability of YourKit Java Profiler 5.5
The newer version offers the following enhancements:
New and improved platform support
- Mac OS X on Intel is supported
- IBM Java 5.0 supported. Important! IBM Java 5.0 Service Release 1 (SR1) or newer is required. Initial IBM Java 5.0 release is not supported because it contains critical bugs in JVMTI implementation.
- BEA JRockit 5 support improvements. Read about known issues
- Telemetry for Java 1.3 and 1.4 is supported as well
- New tab "CPU and Memory"
- Optimization: telemetry information requires less memory in UI
- New profiling mode that provides both method CPU times and invocation counts, but does not monitor internals of methods from core library classes (java.*, javax.*, com.sun.*, sun.*). The benefit is in much smaller overhead than when all methods are monitored.
- In the mode where only CPU times are recorded, accuracy was improved on Linux, Mac OS X and Solaris
- Increased accuracy of CPU times and invocation count measuring mode on Windows and Solaris. In particular, this improves profiling of short running methods.
- Reduced overhead when method invocation counts are recorded
- New feature: now it is possible to import memory snapshots in HPROF binary format. Use "File | Import HPROF Snapshot..." action. Such snapshots are created:
*Automatically by JVM if application fails with java.lang.OutOfMemoryError. To switch this behaviour on, -XX:+HeapDumpOnOutOfMemoryError JVM option should be specified. This option is supported in Java 6 "Mustang" JVM, and will be backported to Java 5.0 update 7 and Java 1.4.2_12.
*Explicitly connecting via jmap utility to any running Sun JVM - no need for extra configuration (works in Java 6 "Mustang", and, possibly not very reliable, on Solaris with Java 1.4.2_09 and newer, and Linux with Java 5.0).
*By JVM's built-in HPROF profiler (not very useful though). Please read more in the bundled Help.
- Reduced overhead of object allocation recording
- Profiler UI can run with Java 6 "Mustang."
Message was edited by: email@example.com