Moritz Halbritter @mhalbritter mhalbritter.github.io Step up the performance game with Spring Boot and Project Leyden 

Why do we care about runtime efficiency? Cheaper hosting Sustainability Optimized containers 

We’re going to take a look at 3 variants CDS AOT Cache AOT Cache with profiling and code compilation 

Workflow Training run Cache Deployment run Startup Fast startup even on cheap servers or scale to zero Memory More applications on less servers Warmup Peak performance immediately 

Optimize your Spring Boot applications with CDS 

Requirements for Spring Boot with CDS Java 17+ Spring Boot 3.3+ 

java -Dspring.context.exit=onRefresh Start Exit on Refresh non-lazy singletons instantiated afterPropertiesSet invoked Lifecycle start invoked ContextRefreshedEvent published Running 

Self-extracting executable JARs my-app.jar 35 MB java -Djarmode=tools -jar my-app.jar extract my-app/ lib/ my-app.jar 0.7 MB Library jars as files for optimized class loading Application classes + manifest file defining the classpath java -jar my-app/my-app.jar 

No content

Spring Petclinic startup time (seconds) 1.2x 1.9x 2.2x 

Spring Petclinic RSS memory (MB) 3.3% 19.1% 19.6% 

CDS requirements JVM The same JVM must be used. Classpath Must be specified as a list of jars. No directories, no wildcard, no nested jars. Deployment classpath must be a superset of the training one. Files The timestamps of the jars must be preserved. Training run When/how to do the training run? Application may try to connect to remote services like databases. 

Training run configuration for your database https://github.com/spring-projects/spring-lifecycle-smoke-tests/tree/main#training-run-configuration 

Training run configuration for your database 

CDS support in Buildpacks Spring Boot Buildpacks + mvn spring-boot:build-image gradle bootBuildImage = The CDS training run is performed transparently when building the container image, ensuring that the same JVM is used 

No content

Optimize your Spring Boot applications with AOT Cache 

AOT Cache and Spring AOT are different - but combine well AOT Cache JVM feature developed via Project Leyden to improve the efficiency of the JVM. It supersedes CDS. Spring AOT Spring feature mandatory for GraalVM native images support. Can also be used on the JVM to speed up the startup process and lower the memory consumption. Precomputes the bean arrangement for specific Spring profiles [1]. [1] https://github.com/sdeleuze/demo-profile-aot 

No content

Requirements for Spring Boot with AOT Cache Java 24+ Spring Boot 3.3+ 

No content

Spring Petclinic startup time (seconds) 1.2x 1.9x 2.2x 2.6x 

Spring Petclinic RSS memory (MB) 3.3% 19.1% 19.1% 22.7% 

Whatʼs coming next via Project Leyden? 

No content

No content

No content

No content

Spring Petclinic startup time (seconds) 1.2x 2.2x 3.9x 4.4x 

4.4x 

440% 

JVM warmup compared Time elapsed (s) Requests / s 

Comparing GraalVM, Project CRaC and AOT Cache 

Moritz Halbritter @mhalbritter mhalbritter.github.io THANKS!!! 

SLIDE TITLE • Bullet 1 • Sub-bullet • Bullet 2 • Bullet 3 • Bullet 4