RFR: JDK-8289524: Add JFR JIT restart event [v2]
Markus Grönlund
mgronlun at openjdk.org
Thu Jul 7 10:40:26 UTC 2022
On Thu, 7 Jul 2022 08:27:54 GMT, Lutz Schmidt <lucy at openjdk.org> wrote:
> So is the common opinion to get back to a separate JIT start event (I think that naming is prefered over JIT restart, am I correct) ? Additionally we add CodeCache:max_capacity() at both JIT start and EventCodeCacheFull ?
I think it is fine to use the term "JIT restart" because it is in use both in the code as well as in the output of log statements. Another reason would be that the first "JIT start" event would always be missing. It was only the meaning that got me a bit confused. Yes, a separate event is preferrable having no duration (startTime=false), no stack trace (stackTrace=false).
The .jfc configs only need one element:
<setting name="enabled" control="compiler-enabled">true</setting>
-------------
PR: https://git.openjdk.org/jdk/pull/9334
More information about the hotspot-dev
mailing list