[~coleenp] mentioned this RFE during the JDK-8253064 review:
src/hotspot/share/runtime/globals.hpp
"The maximum number of monitors to deflate, unlink and delete " \
"at one time (minimum is 1024).") \
range(1024, max_jint) \
\
product(intx, MonitorUsedDeflationThreshold, 90, EXPERIMENTAL, \
"Percentage of used monitors before triggering deflation (0 is " \
"off). The check is performed on GuaranteedSafepointInterval " \
Should there still be experimental options after this change?
@dcubed-ojdk
Robbin added MonitorUsedDeflationThreshold as an experimental
option back in JDK10. See the longer reply to David's comment.
I don't plan to change that option with this changeset.
src/hotspot/share/runtime/globals.hpp
"The maximum number of monitors to deflate, unlink and delete " \
"at one time (minimum is 1024).") \
range(1024, max_jint) \
\
product(intx, MonitorUsedDeflationThreshold, 90, EXPERIMENTAL, \
"Percentage of used monitors before triggering deflation (0 is " \
"off). The check is performed on GuaranteedSafepointInterval " \
Should there still be experimental options after this change?
@dcubed-ojdk
Robbin added MonitorUsedDeflationThreshold as an experimental
option back in JDK10. See the longer reply to David's comment.
I don't plan to change that option with this changeset.
- relates to
-
JDK-8181859 Monitor deflation is not checked in cleanup path
-
- Resolved
-
-
JDK-8226416 MonitorUsedDeflationThreshold can cause repeated async deflation requests
-
- Resolved
-
-
JDK-8253064 monitor list simplifications and getting rid of TSM
-
- Resolved
-
-
JDK-8264420 Allow MonitorUsedDeflationThreshold=0 for aggressive deflation of all eligible monitors
-
- Closed
-
(1 links to)