RFR: 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests [v6]
David Holmes
dholmes at openjdk.java.net
Thu Jan 14 01:22:04 UTC 2021
On Thu, 14 Jan 2021 01:12:18 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:
>> Adding support for a diagnostic option called NoAsyncDeflationProgressMax
>> with a default value of 3. If we have three async monitor deflation cycles in a
>> row with zero monitors deflated, then we adjust the in_use_list_ceiling up.
>>
>> I've locally built and tested this fix on my MBP13 using the
>> MonitorUsedDeflationThresholdTest.java test that I wrote when this issue
>> first came up in June of 2019. I will be including this fix in my next Mach5
>> Tier[1-3] testing batch.
>
> Daniel D. Daugherty has updated the pull request incrementally with one additional commit since the last revision:
>
> address more dholmes CR comments.
LGTM! :)
Thanks,
David
-------------
Marked as reviewed by dholmes (Reviewer).
PR: https://git.openjdk.java.net/jdk/pull/1993
More information about the hotspot-runtime-dev
mailing list