With Java 21, Your Code Runs Even Faster But How is that Possible? By Per Minborg

For most workloads, Java 21 is the fastest Java version ever released. In this short talk, we will take a peak under the hood and explore some of the performance improvements that were made in recent Java versions and how old classes even from Java 1.0 (like RandomAccessFile) were made much faster with no change in user code calling the improved classes. We will also explore some future enhancement candidates and learn how performance is usually measured by committers to the Open JDK. Buckle up for a quick ride!
PER MINBORG
Per Minborg works in the Java Core Library team at Oracle, is an OpenJDK contributor, and is also a member of the Panama project team focusing on the FFM API. He is an inventor and developer with more than 20 years of Java coding experience. He has been a frequent contributor to various open-source projects, is a regular speaker at events, Oracle JavaOne alumnus, and co-author of the publication Modern Java.

[@thoriig3887]

Greetings Per, great work and great improvements from you. i started to compare the enhancements between jdk11 and 21 (after watched your talk at the devoxx) because most of our legacy applications rely on jdk11 and builded a jhm testsuit with more practical workload to show the performance improvements. its amazing. hopefully besides all the new cool features also that will help to get a feet into the jdk21 door and convincing the stakeholders to invest more capacity in modernization. 👍

[@onionhead0708]

Amazing~!! Great to know that we don't need to do anything but just upgrade the JDK to get performance improvement. Thanks~!

[@TaranovskiAlex]

Thank you! Awesome talk!

[@brucedsm]

Nice!

[@b1ueocean]

Damn, all this just to get Java to the starting block 🤷‍♂️ After 20+ years being paid to: - adopt the litany of horrible engineering habits encouraged by the community - exhaust corporate budgets and cost centres through prescribed inefficiency at the team, process, software and management/maintenance levels - pollute code repositories with feature and feature testing verbosity, abstraction onions and boilerplate I’m finally free having decided to render modern c++ the primary implementation language at my startup. Will always prefer to have devs focus on reusable memory-safe libraries in-house than tackle every crazy consideration that goes into producing highly performant, consistent and efficiently scalable Java 😳 Roll on 2024 🎉