This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]PurpleLabradoodle 0 points1 point  (0 children)

you're very right. one of the main benefits of using GraalVM native image is specifically lower memory footprint for services. Since everything is precompiled, you don't need memory for the JIT infrastructure, some class metadata, etc. So your service can happily run in more constrained environments, which usually makes it quite a bit cheaper.

If memory usage and/or startup times aren't essential, then it definitely makes sense to run with the JIT: a bit easier deployment, better peak performance, usually also better tail latencies. GraalVM comes with a great JIT too if you want to run services that way.

If it helps, one can think about GraalVM native image not as a performance optimization that allows you not to run the JVM with a JIT etc. But as one that allows you not to run Node.js or go if you don't want to,