RFR: Do not apply evacuation budgets in non-generational mode

William Kemper wkemper at openjdk.org
Fri Nov 18 00:34:19 UTC 2022


On Thu, 17 Nov 2022 23:15:28 GMT, William Kemper <wkemper at openjdk.org> wrote:

> CSet selection for non-generational mode was using a value configured on the young generation. In non-generational modes we do not maintain all the attributes of the young generation (instead we maintain the _global_ generation). This caused many cycles in which the maximum CSet was zero (or close to it). This, in turn, caused the collector to run much more frequently (approximately 3x on specjbb) which caused severe performance regression in critical jops.
> 
> I'm not sure why the diff algorithm is struggling so much with these changes. I pulled up the `mode()->is_generational()` out of `compute_evacuation_budgets` and `adjust_evacuation_budgets` into the caller and replaced the check with an assert (re-indenting the code in the method).

Try hiding whitespace on github - looks much better to me:

![image](https://user-images.githubusercontent.com/71722661/202588802-a768c9f4-f3fb-45d6-99f5-08b1b75f270a.png)

-------------

PR: https://git.openjdk.org/shenandoah/pull/171


More information about the shenandoah-dev mailing list