During initialization of the CMTask G1 resets the stats table, effectively pre-touching it.
This sometimes shows up in startup profiles, so maybe by not doing it at startup we avoid some pre-touching of that area, but at least avoid doing the work.
The tables will be reset during mark start anyways.
See also JDK-8367993
This sometimes shows up in startup profiles, so maybe by not doing it at startup we avoid some pre-touching of that area, but at least avoid doing the work.
The tables will be reset during mark start anyways.
See also JDK-8367993
- relates to
-
JDK-8367993 G1: Speed up ConcurrentMark initialization
-
- Open
-
-
JDK-8359802 JEP 523: Make G1 the Default Garbage Collector in All Environments
-
- Candidate
-
- links to
-
Commit(master)
openjdk/jdk/2e99ed64
-
Review(master)
openjdk/jdk/27390