Part 3 of a series on Project Leyden's approach to improving Java startup, warmup, and footprint. Covers the internals of the AOT cache including static/dynamic data, JVM metadata, profile and linkage data, compiled methods, and training data. Also introduces a practical diagnostic workflow using a sample Quarkus application to

16m read timeFrom foojay.io
Post cover image
Table of contents
What is inside the Ahead of Time Cache?How Do I Know Leyden Is Helping?Training the applicationAnalyzing the Cache

Sort: