JDK-8308983 : Let UseGCOverheadLimit work independently of UseAdaptiveSizePolicy in parallel GC
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 21
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2023-05-27
  • Updated: 2025-09-25
  • Resolved: 2025-09-25
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
Duplicate :  
JDK-8338977 - Parallel: Improve heap resizing heuristics
Relates :  
JDK-8194823 - Serial GC does not account GCs caused by TLAB allocation in GC overhead limit
Relates :  
JDK-8212206 - Refactor AdaptiveSizePolicy to separate out code related to GC overhead
Relates :  
JDK-8212084 - Implement UseGCOverheadLimit for G1
Description
During the review of JDK-8194823, we find the flag `UseGCOverheadLimit` is only used by parallel GC when the `UseAdaptiveSizePolicy` is true.

Actually, after JDK-8212206, the `UseGCOverheadLimit` can work independently of `UseAdaptiveSizePolicy`. It is good to adjust the implementation in parallel GC to let `UseGCOverheadLimit` work without `UseAdaptiveSizePolicy`.

The related code is at `PSScavenge::invoke_no_policy` and `PSParallelCompact::invoke_no_policy`.
Comments
I think JDK-8338977 decouples these two flags, so they can work independently.
24-09-2025