News for hackers. Stuff that matters.
Re:GraalVM 22.3: JDK 19 builds, jlink support, new monitorin... by pjmlp on Wednesday October 26, 2022 @09:11AM (#33343129)
The problem with deoptimization is the performance hit every time it takes place, which leads to a saw graph similar to when there is too much GC going on.
Re:GraalVM 22.3: JDK 19 builds, jlink support, new monitorin... by kaba0 on Wednesday October 26, 2022 @11:05AM (#33344823)
Sure, but class loading only changes assumptions in one direction for example — in the aforementioned example it would cause only one deoptimization after which the code won’t be worse off than the AOT compiled one. So the JIT case before class load may perform better, and afterwards will perform the same.
Re:GraalVM 22.3: JDK 19 builds, jlink support, new monitorin... by pjmlp on Wednesday October 26, 2022 @12:35PM (#33346133)
Classes can also be unloaded.

What JIT does definitely better is when coupled with PGO data that survives between execution sessions.