JDK-6934758 : Expose the break down of clean up task time during Safepoint
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs17
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-03-13
  • Updated: 2010-09-24
  • Resolved: 2010-07-02
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
6u19-revFixed 7Fixed hs16.2Fixed
Related Reports
Relates :  
Several customers have complained about clean up task takes longer time than they should be. The current source print the break down time when TraceSafepoint is on. But TraceSafepoint is a develop flag and also will enable printing a lot of information regarding safepoint. So this CR needs to address the exposure of these times and also make sure as less overheads as possible.

The solution is to have a new flag "-XX:+TraceCleanupTimeInSafepoint" and print out the time spent in each clean up tasks when that is on. The time stamp will also be printed out when PrintGCTimeStamp is on.

EVALUATION http://hg.openjdk.java.net/hsx/hsx17/master/rev/1753407b5d19

EVALUATION sync from 6u19-rev-b07

EVALUATION http://hg.openjdk.java.net/hsx/hsx17/baseline/rev/1753407b5d19

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/0f6600cee529,ChangeRequest=6934758

EVALUATION I think TraceSafepointCleanupTime might be a better name for that flag.

EVALUATION Use a new flag -XX:+TraceCleanupTimeInSafepoint to enable tracing the clean up task time.