Integrated: 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests
Daniel D.Daugherty
dcubed at openjdk.java.net
Thu Jan 14 14:27:08 UTC 2021
On Thu, 7 Jan 2021 23:14:17 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.
This pull request has now been integrated.
Changeset: be57cf14
Author: Daniel D. Daugherty <dcubed at openjdk.org>
URL: https://git.openjdk.java.net/jdk/commit/be57cf14
Stats: 175 lines in 3 files changed: 168 ins; 0 del; 7 mod
8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests
Reviewed-by: dholmes, coleenp
-------------
PR: https://git.openjdk.java.net/jdk/pull/1993
More information about the hotspot-runtime-dev
mailing list