During initial mark in the gc pause we mark all roots and the promoted objects as live.
The second part is not required at all. The promoted objects could be marked in the scan root regions phase in addition to scanning them.
If that were done, it would decrease the amount of time spent (and the special handling in the code) for initial mark.
The reason for this is mostly removing code in the evacuation, i.e. kind of cleanup. There could be improvements in the evacuation time as well.
The second part is not required at all. The promoted objects could be marked in the scan root regions phase in addition to scanning them.
If that were done, it would decrease the amount of time spent (and the special handling in the code) for initial mark.
The reason for this is mostly removing code in the evacuation, i.e. kind of cleanup. There could be improvements in the evacuation time as well.
- duplicates
-
JDK-8030860 Concurrent start pause initial mark time should be anticipated in G1 young gen sizing
-
- Closed
-
- relates to
-
JDK-8234177 Limit special casing of object copy costs to initial mark
-
- Closed
-
-
JDK-8030860 Concurrent start pause initial mark time should be anticipated in G1 young gen sizing
-
- Closed
-