Downloaded 10 times
Uploaded byAlina Yurenko
Going AOT: Everything you need to know about GraalVM for Java applications
The document presents an overview of GraalVM, an advanced JDK that includes ahead-of-time (AOT) native image compilation, improving Java application performance and resource efficiency. It highlights the framework's capabilities, success stories, and best practices, alongside recommendations for building cloud-native applications and optimizing performance. The discussion also touches upon upcoming features and the importance of community support in enhancing developer experience.
Going AOT: Everything you need to know about GraalVM for Java applications
- 1. @alina_yurenko #DevoxxPL Going AOT: Everythingyou need to know about GraalVM for Java applications Alina Yurenko Oracle Platinum Sponsors
- 2. • Alina Yurenko/ @alina_yurenko • Developer Advocate for GraalVM at Oracle • Love open source and communities 🤝 • Love both programming 👩💻 & natural languages 🗣 •🐱🐶 About me
- 3.
- 4. An advanced JDKwith ahead-of-time Native Image compilation
- 5.
- 6. 2017 Year 2018 20192020 2021 2022 2023 2005 2011 ... ... Sun Labs’ Maxine Java JVM initial release December Native Image open sourced April Twitter uses Graal JIT for core microservices October Micronaut 1.0 with Native Image support April GraalVM 1.0 released April Thomas Wuerthinger joins Oracle and starts Graal compiler project March Spring Native goes beta November Quarkus 1.0 with Native Image support May GraalVM goes GA (19.0 release) September MicroDoc announces GraalVM for embedded July Alibaba deploys Native Image in production July Facebook deploys GraalVM in production May AWS SDK support for Native Image November Spring Boot 3 with Native Image support December OpenJDK Galahad project proposed July Google Cloud Platform SDK support for Native Image June GraalVM Free Terms and Conditions license September GraalOS & Layered Native Image announced March Azure SDK support for Native Image September Oracle Cloud runs services on GraalVM Graal History 🎉 🎉 🎉
- 7. GraalVM Native ImageAOT Compilation Ahead-of-Time Compilation Application Libraries JDK Substrate VM Points-to Analysis Run Initializations Heap Snapshotting Input: All classes from application, libraries, and VM Code in Text Section Image Heap in Data Section Image Heap Writing Output: Native executable • shift work to build time 🏗️ • closed-world assumption 🔮
- 8.
- 9. GraalVM Native Image—FastStart Up and Much More Improved Security Fast Start & Scale Lower Resource Usage Compact Packaging Predictable Performance Supported Azure AWS GCP OCI
- 10.
- 11. GraalVM Native ImageAOT Compilation Ahead-of-Time Compilation Application Libraries JDK Substrate VM Points-to Analysis Run Initializations Heap Snapshotting Input: All classes from application, libraries, and VM Code in Text Section Image Heap in Data Section Image Heap Writing Output: Native executable • shift work to build time 🏗️ • closed-world assumption 🔮
- 12. NATIVE IMAGE BUILD-TIME DISCOVERY AND CONFIGURATION SPRINGBOOT RUN-TIME DISCOVERY AND CONFIGURATION
- 13. SPRING BOOT NATIVEIMAGE SPRING AOT
- 14.
- 15. SPRING AOT JAVA SOURCEFILES BYTECODE HINT FILES
- 16.
- 17. Libraries, dynamic Javafeatures, and Native Image • Libraries might be Native-Image friendly out of the box • twitter.com/YunaMorgenstern/status/1729039787351536084 • Libraries might include config for Native Image: • github.com/h2database/h2database/blob/master/h2/src/main/META-INF/native-image/ • Libraries might contain config in the Reachability Metadata Repository • github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/io.netty • You can use framework support to produce custom “hints” for Native Image runtimeHints.resources().registerPattern(“config/app.properties”); • You can use the Tracing Agent to produce the necessary config automatically • graalvm.org/latest/reference-manual/native-image/metadata/AutomaticMetadataCollection/ • You can provide/extend config for reflection, JNI, resources, serialization, and predefined classes manually in JSON: • graalvm.org/latest/reference-manual/native-image/metadata/#specifying-metadata-with-json Happy path; most of the cases Custom code/ libraries
- 18. Ready for GraalVMNative Image graalvm.org/native-image/libraries-and-frameworks
- 19.
- 20. AOT at thespeed of JIT 🚀 • Profile-guided optimizations Collect and use profiles at build time to optimize for the specific runtime behaviour of your application • ML-enabled PGO Use a ML model to automatically predict the profile of the application • G1 GC Optimize GC for peak throughput • `-march=native` Optimize for the specific hardware features of the machine you’ll be running on
- 21. Spring PetClinic: MemoryEfficiency
- 22. Spring PetClinic Performanceon Oracle GraalVM GraalVM CE with C2 JIT Oracle GraalVM Native Image Memory Usage (max RSS) 1,029 MB 641 MB Peak throughput 11,066 req/s 11,902 req/s Throughput per memory 12,488 req/(GB*s) 18,569 req/(GB*s) Tail latency (P99) 7.2ms 5.15ms Startup 7,090ms 210ms -38% lower +8% higher +49% better -28% lower 34x faster
- 23.
- 24. Cross-Platform Builds onGitHub Actions Windows Executable macOS Executable Linux Executable .class .jar .class .jar GraalVM GitHub Action 🏗🤝
- 25. • Migrate 🚀 •Add Native Build Tools • Alternatively, use recent versions of frameworks • Evaluate libraries: graalvm.org/native-image/libraries-and-frameworks • Build and deploy 👷♀️ • Build and test on GraalVM as the JVM, build with Native Image closer to the deployment • Quick build mode with `-Ob` • Use CI/CD systems (e.g. GitHub actions) for deployment and cross-platform builds • Run faster 🚀 • PGO • ML-enabled PGO • G1 GC • `-march=native` Recommendations
- 26.
- 27. • Java 22features • The fastest GraalVM yet :) • Developer experience improvements Learn more: medium.com/graalvm GraalVM for JDK 22 🚀
- 28. Layered Native Images Micronautbase Micronaut extensions (Web, Data, Test) Spring base App 1 App 2 App 3 Deployment: resources sharing ☁️ JDK base Application code Development: fast recompilation 🚀 JDK base + Micronaut base+ all extensions App 4
- 29. GraalOS—Advanced cloud nativeapplication deployment platform Fast Start GraalOS applications start fast with virtually no cold start cost Low Latency Excellent 99th percentile latency makes GraalOS applications highly responsive Run On Demand GraalOS applications are automatically suspended and resumed on demand—with no idle cost Applications, not Containers GraalOS uses the latest advances in x86 and AArch64 processor architectures for hardware enforced application isolation without containers Reduced Memory GraalOS applications require significantly less memory resulting in reduced operating costs Cloud Native With support for stateful and stateless services and functions, GraalOS is ideal for cloud native applications Runs applications as small, fast GraalVM Native Image compiled machine executables
- 30. Compact Packaging GraalVM Native Image—Idealfor Cloud Native Applications Improved Security Fast Start & Scale Lower Resource Usage Predictable Performance Supported Azure AWS GCP OCI
- 31. Questions & let’sconnect! Demos 👩💻
- 32. Please rate thissession :) 🐈
- 33.
Editor's Notes
- #37 What is GraalOS? GraalOS is a high performance serverless Java-based application deployment platform. It uses GraalVM Native Image to run your application as a native machine executable—taking full advantage of the latest x64 and AArch64 processor features available on Oracle Cloud Infrastructure (OCI). An application deployed to GraalOS will be less expensive to operate and help reduce your cloud costs. Fast Start A GraalOS application starts fast with virtually no “cold start” cost. Unlike container-based platforms that suffer from significant cold start costs, a GraalOS application is a small native Linux executable that starts in 10s of milliseconds. Reduced Memory A GraalOS application requires significantly less memory thanks to GraalVM Native Image ahead-of-time (AOT) compilation. In turn, lower memory usage has a direct impact on your operating costs: pricing structures for most cloud services, including OCI Functions, have a significant memory usage element. GraalOS can typically reduce your application memory by at least 50%. Run On Demand A GraalOS application is automatically suspended and resumed when called—with no idle cost. Applications and functions that are not receiving requests are terminated on most serverless platforms after a timeout period has been exceeded. An application that is subsequently invoked is subject to a cold start cost. GraalOS’s ability to suspend and rapidly resume your idle applications means no cold start. Applications, not Containers GraalOS runs native Linux executables directly—taking advantage of the latest advances in hardware-enforced application isolation. This approach removes the need to package your application into a container, which eliminates challenges such as selecting a secure container image and ensuring that the latest security patches are in place and updated regularly. Cloud Native With support for stateful and stateless microservices and functions, GraalOS is ideal for cloud native applications. Both short-lived functions and long-running microservices will benefit from GraalOS features such as virtually no cold start, transparent suspend and resume, and no cost idle. OCI Functions Powered by GraalOS The first use of GraalOS is in OCI Functions: it will add a new “Graal Function” type that will start much faster and require less memory than existing OCI functions. Thanks to the built-in OCI Functions triggers provided by OCI services such as Events, Connector Hub, Data Integration, API Gateway, and Notifications, all these services will be able to take advantage of GraalOS-powered functions with no changes. To learn more, see Rishikesh Palve’s blog “Ultra-fast Serverless Functions Powered by GraalOS”.