JDK-6935224 : Adding new DTrace probes to work with Palantir
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs17
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-03-16
  • Updated: 2017-05-16
  • Resolved: 2010-04-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u21pFixed 7 b88Fixed hs18Fixed
Related Reports
Relates :  
JDK-6274545 - Add dtrace probes for tracing Java program
Description
Improving the support of the DTrace provider to provide better reporting to the Palantir tool.
Comments
EVALUATION ChangeSet=http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/e392695de029,ChangeRequest=6935224
17-03-2010
EVALUATION Palantir is a tool designed to analyze the behavior of multithreaded applications. Data collection is performed with DTrace scripts. The current DTrace instrumentation of HotSpot suffers from two main issues. The first one is the lack of instrumentation of some areas of the virtual machine. The second issue is the significant overhead caused by some probes (object allocations and method invocation). The goal of this work is to improve the current hotspot DTrace provider to provide more data to the Palantir tool while preserving a low overhead. *** (#1 of 1): [ UNSAVED ] ###@###.###
16-03-2010
SUGGESTED FIX The first step to improve the hotspot provider consists of: - adding probes related to thread scheduling (sleep, yield, park/unpark) - adding probes related to class initialization - adding support for dynamic activation of the monitor related probes (without activating the method/allocations probes which cause a big performance overhead) *** (#1 of 1): [ UNSAVED ] ###@###.###
16-03-2010