Quarkus 3.11: native executable has almost twice less throughput than JVM one about quarkus HOT 5 CLOSED

/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel,native-image)

from quarkus.

Hello @nicolasduminil

I'd expect that the number of requests per second of the application running in native executable mode be much higher than the one running in JVM mode.

Why do you expect that? Please have a look at this detailed answer on a similar issue oracle/graal#979 (comment)

To better understand what's happening specifically in your case you may have a look at https://github.com/quarkusio/quarkus/blob/main/TROUBLESHOOTING.md#troubleshooting-performance-issues

Hope that helps

from quarkus.

@zakkak Many thanks for sending me links to how to profile the code but this wasn't at all my point. At least you're making clear that running native executable is much slower (twice) than running in JVM. It's not very intuitive that interpreting the code might be faster than executing native code, that's why I (and Im not the only one) was expecting a very different result. But it's good to know anyway. AFAIC, if the only benefit of native executable is the startup time and the footprint for the price of much less throughput, then not for me.

from quarkus.

It really depends on the application and your needs (higher throughput, higher throughput per watt, faster start up, less energy consumption, etc.). If your benchmarks indicate that native executables are not covering your needs, or that the trade offs are not worth it, then you are probably right. Happy that I was able to help.

from quarkus.

... It's not very intuitive that interpreting the code might be faster than executing native code...

Maybe you need to brush up a bit on HotSpot, in particular the JIT ;)

from quarkus.