Today cleanup is only triggered by IC buffers that needs to be finiliazed.
This cleanup check is done in every GuaranteedSafepointInterval (default 1s).
If the cleanup check return false there will be no safepoint, so the option name, GuaranteedSafepointInterval, is misleading.
This makes the time between safepoint potentials much longer after the compiler stabilize and can have a big negative affect on the numbers of monitor, thus also latency.
This cleanup check is done in every GuaranteedSafepointInterval (default 1s).
If the cleanup check return false there will be no safepoint, so the option name, GuaranteedSafepointInterval, is misleading.
This makes the time between safepoint potentials much longer after the compiler stabilize and can have a big negative affect on the numbers of monitor, thus also latency.
- relates to
-
JDK-8226416 MonitorUsedDeflationThreshold can cause repeated async deflation requests
-
- Resolved
-
-
JDK-8230938 Deprecate MonitorBound
-
- Resolved
-
-
JDK-8256304 should MonitorUsedDeflationThreshold be experimental or diagnostic
-
- Resolved
-