JDK-8368082 : G1: More lazily initialize concurrent refinement
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-09-19
  • Updated: 2025-09-19
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
tbdUnresolved
Related Reports
Relates :  
JDK-8359802 - JEP 523: Make G1 the Default Garbage Collector in All Environments
Description
During startup initializing concurrent refinement (threads) shows up in profiles.

Concurrent refinement is not necessary until after the first old gen region has been allocated (~after first gc), so it might be possible to move all that initialization out of startup to increase its performance.

See JDK-8367993 for a potential startup benchmark/profile.