JDK-8367992 : Card table clearing during commit significantly slows down VM startup
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-09-18
  • 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 :  
Relates :  
Relates :  
Relates :  
Description
Since the clean card value for the card table is defined as 0xff, all collectors using card table need to reset its values to that value.

This is an implicit pre-touch of all the memory of the card table, which slows down startup.

The reason why this value has been selected is (apparently) to reduce the barrier code: many architectures have zero-valued registers, so when dirtying (setting to zero) the barrier code does not need to load the dirty card value (0x00) into a register.

Evaluate the costs of changing this, or find another method to avoid touching these cards during startup.