![WHY NOT… ?
• No Dynamic class Loading / Unloading
• No JVMTI, Java Agents, JMX, JFR support
• Efficient only for smaller heap [Due to
serial GC]
• No thread dump and heap dump
support
• Opaqueness with reflection
• Generated native code is not fully
efficient while using profiling [Due to no
access for application runtime profile]](https://image.slidesharecdn.com/graalvm-210311102133/85/Introduction-to-GraalVM-11-320.jpg)
Introduction to GraalVM
- 1. RUN PROGRAMS FASTER ANYWHERE
- 2. CONTENTS WHAT IS GRAALVM? HOTSPOT VM VS GRAALVM GRAALVM ARCHITECTURE WHY GRAALVM? USE-CASES
- 3. GRAALVM A high-performance multilingual runtime. It is designed to accelerate the execution of applications written in Java and other JVM languages while also providing runtimes for JavaScript, Ruby, Python, and a number of other popular languages. Know more at https://www.graalvm.org/
- 4. HotSpot VM vs GraalVM • Graal is part of JDK from OpenJDK 9+ . • Graal is the new JIT (Just in time) compiler which will replace C2. • Graal distinguishes between image build time and image run time. At image build time, a static analysis finds all methods that are reachable from the entry point of the application and these methods are then ahead-of- time compiled into a native image.
- 5. JIT vs AOT Just-in-time Compiler Ahead-of-time Compiler Compiles while running Compiles before running Dynamic compilation Static compilation Runtime information More resources De-optimization Way more time Typical for JVM Uncommon for JVM (JDK 9+)
- 7. NATIVE RUNTIME • Substrate VM is an internal project name for the technology behind GraalVM Native Image. • Native Image is a technology to ahead-of-time compile Java code to a standalone executable, called a native image. • GraalVM is a hybrid of static and dynamic runtimes.
- 8. GRAAL COMPILER DEMO This demo example counts the number of uppercase characters in a body of text. To simulate a large load, the same sentence is processed 10 million times:
- 9. PERFORMANCE GRAPH Loop C1 + C2 Graal 1 510 1581 2 375 480 3 365 364 4 368 231 5 348 196 6 370 121 7 353 116 8 348 116 9 369 116 0 1000 2000 0 2 4 6 8 10 Comparison C1 + C2 Graal
- 10. WHY GRAALVM? • Fast start-up Java Application: Native • Low footprint ahead-of-time mode for JVM-based languages • High performance for all languages • Convenient language interoperability and polyglot tooling • Java as Language Platform • Embedded Java Application
- 11. WHY NOT… ? • No Dynamic class Loading / Unloading • No JVMTI, Java Agents, JMX, JFR support • Efficient only for smaller heap [Due to serial GC] • No thread dump and heap dump support • Opaqueness with reflection • Generated native code is not fully efficient while using profiling [Due to no access for application runtime profile]
- 12. USECASES SUBSTRATEVM • Command-line tools • Embedded / Constrained devices (note: ARM is not supported for SVM yet) • Containerized environments where raw performance is not the main concern JVM + GRAAL JIT COMPILER • Services, Networked services, Micro- services, • Data processing applications where performance is critical • Alternative JVM languages
- 13. REFERENCES • https://www.baeldung.com/graal-java-jit-compiler • https://jponge.medium.com/the-graalvm-frenzy- f54257f5932c • https://www.graalvm.org/reference- manual/native-image/Limitations/ • https://medium.com/graalvm/graalvm-native- image-quick-reference-4ceb84560fd8
- 14. THANK YOU