Java Performance Update
summary
Roadmap and concrete wins: Project Leyden targets large reductions in startup and warmup by persisting profiling and compiled code into an AOT cache so many apps start “fast from zero”; string toString shows ~2x improvement in examples; stable deferred immutability via stable values lets the JVM constant-fold lazy-initialized fields with record‑level safety (JEP draft sent for review), and surprisingly some FFM bulk ops run faster in Java than intrinsics with a 64‑byte threshold and long indices for huge memory segments.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:26Project Leyden update
- 6:24Future Java roadmap
- 8:24Stable values explained
- 14:47Stable collections and API
- 17:30FFM API performance
- 20:20Closing remarks
related talks
51mJava Performance Update: From JDK 21 to JDK 25
47mJava Renaissance
41mJava 24, Faster Than Ever
35mJava at Speed: Building a Better JVM
48mJust-In-Time Compilation for Java Performance: Recent and Ongoing Improvements
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
01h 03mKeeping Your Java Hot.
46mProject Leyden's AOT - Shifting Java Startup into High Gear
