In default/profile configurations for the events we have these:
<event name="jdk.JavaMonitorInflate">
<setting name="enabled">false</setting>
<setting name="stackTrace">true</setting>
<setting name="threshold" control="locking-threshold">20 ms</setting>
</event>
There is a threshold for inflate event. But the operation that is covered by that event is very fast, and often lock-free, so the threshold would filter many events. This would be important as we add deflation event (JDK-8351142), which should match inflations.
<event name="jdk.JavaMonitorInflate">
<setting name="enabled">false</setting>
<setting name="stackTrace">true</setting>
<setting name="threshold" control="locking-threshold">20 ms</setting>
</event>
There is a threshold for inflate event. But the operation that is covered by that event is very fast, and often lock-free, so the threshold would filter many events. This would be important as we add deflation event (
- blocks
-
JDK-8351142 Add JFR monitor deflation and statistics events
-
- Resolved
-
-
JDK-8351187 Add JFR monitor notification event
-
- New
-
- relates to
-
JDK-8351142 Add JFR monitor deflation and statistics events
-
- Resolved
-
-
JDK-8348833 Remove ObjectMonitor perf counters
-
- Provisional
-
- links to
-
Commit(master) openjdk/jdk/0ad9a104
-
Review(master) openjdk/jdk/23891
(1 links to)