How Class Data Sharing Can Speed up Your Jakarta EE Application Startup
summary
Shows how to use JDK 17 class data sharing to precompute a classlist dump and build a shared archive so a Jakarta EE app with ~14k classes launches much faster without code changes. Compares OpenJ9 vs HotSpot/OpenJDK behavior and commands, demonstrates creating the archive (classlist → dump → use at startup), and measures startup improvements commonly in the 5–10 second range (examples drop ~6s → ~4.3s) and memory savings around 5–10% in Docker; warns about dynamic proxies/reflection and platform/permission caveats.
AI-written summary · about
chapters (4)
- 0:00Start
- 10:31Improvements? Can we improve this?
- 15:16Why Fast Startup Important? • Large surge in requests
- 18:14Class Data Sharing - CDS • Load, verify, derive - Perform upfront Store info in memory mapped read-only file
related talks
41mImprove Startup Performance and Reduce Footprint with Application Class Data Sharing
35mOptimize your applications to the max with Jakarta EE and MicroProfile
42mTechniques for a faster JVM start-up
46mSimple Tweaks to Get the Most Out of Your JVM
42mSimple tweaks to get the most out of your JVM
57mCould your Java workloads be missing out on something?
35mJava in a world of containers
52mTechniques for a faster JVM start-up
