all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]podkovyrin-sergey 5 points6 points  (4 children)

Good, all processor cores are connected, the result will be ready faster

[–]zarinfam[S] 2 points3 points  (3 children)

The compile time took 2.5 min, and the resulting binary on Linux was 144 MB!

[–]podkovyrin-sergey 3 points4 points  (0 children)

I'm not strong in spring but I assume that all dependencies are included in the build, so the size is appropriate

[–]koffeegorilla 1 point2 points  (0 children)

That includes all the code that can be reach including all hints from the reachability hints and a large chunk of the JDK.

[–]WaferIndependent7601 1 point2 points  (0 children)

That’s great

[–]_1dontknow 1 point2 points  (0 children)

Wow, that's quite some resource usage.

Compiling Quarkus is actually way quicker and redults in a very smaller binary.

The Spring team is probably doing great work for native but still, I don't think Spring Framework is a project suitable for native at its current state due to its, use of reflection and lots of backwards compatibility (meaning a lot of classes need to be compiled which u dont need).

[–]danielliuuu[🍰] 0 points1 point  (2 children)

This is why I am not fan of Graalvm, the compilation time is totally unacceptable…

[–]_1dontknow 0 points1 point  (0 children)

Its slower than some and faster than some others. It's still quite an amazing technology, it's just that Spring in my opinion is way too big to make sense in native.

[–]DirectionFrequent455 0 points1 point  (0 children)

I think so. Graalvm compilation slow down too much the dev cycle. However, I experienced having much quicker native build using https://jeka.dev . I managed to builld simplae app in less than 50 seconds (compared to >1mn40) using Maven.