1 of 13

🚀Java is Going to the Moon: Native Images with GraalVM

+

Small demo

1

2 of 13

Agenda

2

What?
Why?
How?
Demo

3 of 13

going on in Javaland?

What’s

3

4 of 13

going on in Javaland?

What’s

4

https://quarkus.io

https://micronaut.io

https://helidon.io

5 of 13

Why

Quarkus?

5

Fast boot time
Small size on disk
Low RSS memory
Developer joy

Instant scale up
Small container images
More containers with the same RAM

RSS memory -> Resident Set Size

Quarkus, classes used only at application startup are invoked at build time and not loaded into the runtime JVM. Quarkus also avoids reflection as much as possible, instead favoring static class binding. These design principles reduce the size, and ultimately the memory footprint, of the application running on the JVM while also enabling Quarkus to be natively-native.

Quarkus' design accounted for native compilation from the onset. It was optimized for using the native image capability of GraalVM to compile JVM bytecode to a native machine binary. GraalVM aggressively removes any unreachable code found within the application's source code as well as any of its dependencies. Combined with Linux containers and Kubernetes, a Quarkus application runs as a native Linux executable, eliminating the JVM. A Quarkus native executable starts much faster and uses far less memory than a traditional JVM.

6 of 13

Quarkus works?

How?

6

7 of 13

7

Run programs more efficiently
Make developers more productive

https://www.graalvm.org

8 of 13

8

Run programs more efficiently
Make developers more productive

https://www.graalvm.org

9 of 13

9

10 of 13

to create a native image via AOT?

How

10

Wimmer, Christian, et al. "Initialize once, start fast: application initialization at build time." OOPSLA (2019): 1-29.

11 of 13

a close world assumption is necessary

But…

11

The points-to analysis needs to see all the bytecode
Dynamic Java features require configuration at build time
No loading of new classes at run time

12 of 13

RQs

that matter…

12

Is the behavior always preserved? (i.e, compilable code = native code)
How to automatically modify applications to comply with the close world assumption?
What tools are available to analyze the native binary?
…

13 of 13

Demo!

13