RFR: 8319867: GenShen: Make old regions parseable at end of concurrent cycles
William Kemper
wkemper at openjdk.org
Sat Nov 11 00:36:30 UTC 2023
On Fri, 10 Nov 2023 23:47:23 GMT, Y. Srinivas Ramakrishna <ysr at openjdk.org> wrote:
>> ### Background
>> When Shenandoah is performing a concurrent mark of the old generation, it is not safe for the young generation's remembered set scan to use the old mark bitmap. For this reason, any old regions that were not included in a collection set (either mixed or a global collection) must be made _parseable_ for the remembered set scan (we call this "coalescing and filling" in the code).
>>
>> ### Description
>> Before this change, Shenandoah has deferred making these regions parseable until it begins the young generation bootstrap cycle. This is fine, except that we have also recently made old generation collections subordinate to young collections. In other words, an old collection cannot start unless Shenandoah wants to first start a young collection.
>>
>> Unfortunately, the additional time to concurrently coalesce and fill old regions before resetting the old mark bitmaps is not accounted for in the heuristics and this increases the likelihood that the heuristic has started the cycles too late and that the cycle will degenerate into a stop the world pause.
>>
>> After this change, Shenandoah will make old regions parseable immediately following the last mixed collection (or following a global collection). At this point, Shenandoah has just finished reclaiming memory and we expect less urgency to coalesce and fill old regions. It also means that young bootstrap cycles will not take (much) longer than conventional young generation collections.
>
> src/hotspot/share/gc/shenandoah/shenandoahOldGeneration.cpp line 259:
>
>> 257: }
>> 258:
>> 259: // Make the old generation regions parseable, so they can be safely
>
> Nothing to do now, but my ex-colleague Peter Kessler told me many years ago that the correct spelling is "parsable" (without the "e" between the s and the a :-) One can do a cleanup of spelling in a separate PR in the fullness of time.
>
> https://word.tips/spelling/parsable-vs-parseable/
[0] % grep -irI parsable src/ | wc -l
352
[0] % grep -irI parseable src/ | wc -l
84
Indeed. I'll fix up all the misspellings in `gc/shenandoah` in a separate PR. Thanks for the tip!
-------------
PR Review Comment: https://git.openjdk.org/shenandoah/pull/355#discussion_r1390061992
More information about the shenandoah-dev
mailing list