JDK-8243974 : Move G1CollectedHeap::millis_since_last_gc support from G1Policy
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 15
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2020-04-28
  • Updated: 2020-07-06
  • Resolved: 2020-07-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.
Other
tbdResolved
Related Reports
Blocks :  
JDK-8248221 - G1: millis_since_last_gc updated at wrong time
Blocks :  
JDK-8165501 - Serial, Parallel and G1 should track the time since last gc for millis_since_last_gc() with full precision
Duplicate :  
JDK-8248401 - Refactor/unify RMI gc support functionality
Relates :  
JDK-8208390 - G1 should always use ticks as internal time base instead of double
Description
With JDK-8208390 the variable to track G1CollectedHeap::millis_since_last_gc has been separated from G1Policy needed time tracking since G1Policy and G1CollectedHeap::millis_since_last_gc uses a different time source (Ticks vs. os::JavaTimeNanos).

That functionality has not much to do with policy decisions at all. Investigate whether a more appropriate place for that can be found (e.g. G1CollectedHeap).
Comments
JDK-8248401 changes the whole mechanism to make this change obsolete
06-07-2020