Should I Upgrade my Java?
summary
JMH benchmarks use three forks, five warmups and five measurement iterations (15 total) and report ops/sec; results show Java 17 shows higher ops/sec for map.put/get on integers versus Java 8 and 11, with strings showing JDK 11 faster up to ~25k keys and JDK 17 faster above that. Memory probes (used minus free) run on a 4‑core i5 and show reduced heap usage on Java 17. Demonstrations include var, switch expressions (yield), text blocks, helpful NPEs, pattern matching, records and sealed classes; Nashorn and CMS are removed and G1 is default.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:00About Eclipse Collections
- 3:08Performance Benchmarking Setup
- 8:26Map Performance Results
- 14:12Memory Usage Comparison
- 17:23Q&A on Performance
- 18:03Local Variable Type Inference
- 20:54Enhanced Switch Statements
- 25:25Text Blocks for Strings
- 29:18Helpful Null Pointer Exceptions
- 32:54Pattern Matching for Instanceof
- 35:39Java Records Explained
- 39:13Sealed Classes Overview
- 46:48Q&A on Features
- 48:17Removed Java Components
- 50:28Garbage Collector Options
- 50:50Takeaways and Conclusion
related talks
01h 01mShould I Upgrade to Java 17?
40mShould I Upgrade My Java
46mGoing Java::Current in Production
51mJava Performance Update: From JDK 21 to JDK 25
41mJava 24, Faster Than Ever
01h 05mJava 11 to 17 - Exciting New Features
46mBeam Me Up, Java! A Journey through Java LTS Versions 11 to 21
47mBeam Me Up, Java! Unraveling the Warp-Speed Evolution: A Journey through Java