Download to read offline
![Recorder
[ STATIC_INIT |RUNTIME_INIT ]](https://image.slidesharecdn.com/quarkusbootstrap2020-200805140447/75/Quarkus-bootstrap-2020-33-2048.jpg)
Uploaded byMaksym Govorischev
Quarkus bootstrap 2020
The document discusses the optimizations Quarkus makes compared to traditional Java frameworks, focusing on performance, startup time, and memory footprint. It highlights Quarkus's ability to halve resource usage and significantly increase boot speed through its unique build processes and extension mechanisms. The document also explores how Quarkus streamlines application startup by modifying class paths and utilizing tools like GraalVM for native image compilation.
In this document
Powered by AI
Introduction of the Quarkus application and presenter details.
Overview of issues in Java frameworks like class loading, runtime initialization, and need for a full JVM.
Focus on optimizing performance, including startup time and memory footprint for Quarkus applications.
Detailed explanation of the typical startup process in traditional Java frameworks, including packaging and classpath scanning.
Description of how Quarkus optimizes its startup process compared to traditional frameworks.
Details about the build paths for Quarkus, including plugins, optimizations, and extensions.
Technologies and tools supporting Quarkus' features, emphasizing AOT compilation and the extensions mechanism.
Quarkus bootstrap 2020
- 1. DATE OR VENUE QuarkusApplication Bootstrap where do small sizes and timings come from? JAVA MARATHON – JULY 2020
- 2.
- 3. New player -Quarkus
- 4.
- 5. What is wrongwith Java frameworks • They load too many classes • They perform a lot of initialization at runtime • They overuse dynamic/reflective functionality (in general and during startup in particular) • They need to be paired with full-fledged JVM to run
- 6.
- 7. What is beingoptimized? • Performance – startup time
- 8. Performance – startuptime https://dzone.com/articles/micr oservices-quarkus-vs-spring-boot
- 9. What is beingoptimized? • Performance – startup time • Resources – memory footprint (RSS)
- 10. Performance – memoryfootprint https://dzone.com/articles/micr oservices-quarkus-vs-spring-boot
- 11. How faster/smaller? Ruleof thumb Hotspot optimized Quarkus App ½ the RSS space X5 boot speed Native optimized Quarkus App 1/5 the RSS space X50 boot speed @Dimitris Andreadis, Director of Engineering at Red Hat
- 12. What is beingoptimized? • Performance – startup time • Resources – memory footprint (RSS) • Resources – app size
- 13. Why app sizematters? Because of lambdas
- 14.
- 15. How does usualJava framework start?
- 16. How does usualJava framework start? Packaging (maven, gradle)
- 17. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files
- 18. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability
- 19. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability Build metamodel of the world
- 20. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability Build metamodel of the world IO, threadpools, etc
- 21. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability Build metamodel of the world IO, threadpools, etc Build time
- 22. How does usualJava framework start? Packaging (maven, gradle) Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability Build metamodel of the world IO, threadpools, etc Build time Runtime
- 23. How does Quarkusstart? Packaging (maven, gradle)Load and parse config files Classpath scanning and annotation discovery. Enable features based on class availability Build metamodel of the world IO, threadpools, etc Build time Runtime
- 24.
- 25.
- 26.
- 27. Quarkus build paths *.class Maven/Gradleplugin Optimized Jar Extensions
- 28.
- 29.
- 30.
- 31.
- 32. Extensions mechanism Extensions Class-path modification Build augmentation Build StepsBuild Items Bytecode recorders
- 33.
- 34. Tools under thehood Jandex
- 35. Tools under thehood Gizmo Jandex
- 36. Build Augmentation Index Corequarkus-data Parse Config Step Scan Step Repo Init Step app.properties Application.class Static Init RuntimeInit Recorded bytecode ApplicationIndexBuildItem ConfigBuildItem - Build item - Build step
- 37. Quarkus build paths *.class Maven/Gradleplugin Optimized Jar Jlink + AppCDS Extensions
- 38. Quarkus build paths *.class Maven/Gradleplugin Optimized Jar Native executable/image Jlink + AppCDS Extensions
- 39. Tools under thehood Graal Compiler Gizmo SubstrateVM Jandex
- 40.
- 41. AOT Native ImageCompilation with GraalVM
- 42. Extensions mechanism Extensions Class-path modification Build augmentation Build StepsBuild Items SubstrateVM Substitutions Bytecode recorders