RFR: 8212107: VMThread issues and cleanup [v6]

Mon Sep 28 18:36:02 UTC 2020

On Mon, 28 Sep 2020 18:30:01 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

>> All test using SafepointALot the already set the GuaranteedSafepointInterval to a low value in range of ~1-300ms.
>> (except for vm boolean flag test which uses SafepointALot  to test a boolean flag)
>> For example jni/FastGetField sets GuaranteedSafepointInterval to 1.
>> 
>> The only case it would really differ is when adhoc adding SafepointALot without GuaranteedSafepointInterval.
>
> If GuaranteedSafepointInterval is set to a lower value than the default on the command line, then I'm okay if
> SafepointALot does not do anything extra. However, if GuaranteedSafepointInterval is either the default value or is set
> to a higher value, then I would like SafepointALot to cause a safepoint more frequently than the
> GuaranteedSafepointInterval. Every GuaranteedSafepointInterval/4 would be a fine definition of "a lot".

Mulling on this more... is it too radical to consider that we no longer need SafepointALot?

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

PR: https://git.openjdk.java.net/jdk/pull/228