I am not quite convinced to use gralvm trading off with memoryfootprint and boottime against littlepain overhead in reflection, proxies or other management. May be i am wrong. But as @JoshLong well said - this is not the end but the beginning. Hopefully in coming days my impression will change. Great Video from the Great, my alltime favorite, The JoshLong.
I found that it's quite difficult to use GraalVM native image and Spring boot in real world applications. No doubt that Spring has great support for metadata needed for GraalVM native image, however applications typically consist other dependencies, not only from Spring ecosystem. Third party libraries have poor support for GraalVM native images. Even though libraries can be adopted with metadata, it takes a lot of time to create metadata properly. Also GraalVM metadata needs to be reviewed when third party library is updated to a new version.
Although the startup time is ten folds faster it takes way too much memory to build the executable. This is in reference to building a simple spring boot app with a simple database connection 😮💨
Thanks for video ! Very nice ! So, you can show a video about open telemetry. For exemple, how to pass any parameter "-javaagent" at a code compilated by graalVM.
Have the same result but trying to scale to zero, because i think the idea it's that the instances die as fast as possible. I'm having some issues but in GCP connections; in performance we solve it by let each instance live about 5 to 10 minutes
graalvm cannot be trusted , you can end up with coruppted binary. example: objectmapper.wrireObjectAsString will return empty string when compiled to native image
I am not quite convinced to use gralvm trading off with memoryfootprint and boottime against littlepain overhead in reflection, proxies or other management. May be i am wrong. But as @JoshLong well said - this is not the end but the beginning. Hopefully in coming days my impression will change. Great Video from the Great, my alltime favorite, The JoshLong.
I found that it's quite difficult to use GraalVM native image and Spring boot in real world applications.
No doubt that Spring has great support for metadata needed for GraalVM native image, however applications typically consist other dependencies, not only from Spring ecosystem.
Third party libraries have poor support for GraalVM native images. Even though libraries can be adopted with metadata, it takes a lot of time to create metadata properly. Also GraalVM metadata needs to be reviewed when third party library is updated to a new version.
Chapters please!
Thank you Josh for this information. Great video
Although the startup time is ten folds faster it takes way too much memory to build the executable. This is in reference to building a simple spring boot app with a simple database connection 😮💨
it would be nice if you show the demo until deployment, maybe to minikube😄
Oh yes please!
Thanks for video ! Very nice ! So, you can show a video about open telemetry. For exemple, how to pass any parameter "-javaagent" at a code compilated by graalVM.
Can we have spring cloud demo i.e Gateway,Config-server,Eureka
using GraaLVM?
what's that 'uao' command that unzip and open the project? my guess is that was made by you, nice tool
Which version of Intellij Idea is that ?
Intellij New UI, you can enable it.
at 08:00 -> i done the mvn command with `-Pnative` but it not construct the binary :/
FYI: i had to do a `mvn -DskipTests -Pnative native:compile` to generate the binary - i don't know why this different command is needed?
@@Muescha spring-boot:build-image builds a docker image. With the native profile I guess that image contains a natively compiled program.
@@Muescha probably because your are running your tests. mockito doesnt support native builds yet.
Can I use this (Spring 3 + GraalVM) to compile JavaFX Application?
Aot Compiled Programs Start faster Need LEss Memory but Show worse performance. Tested that many times
would you mind sharing how the results look like?
ongoing compiler optimizations on frequently used code segments (hotspots???) make the difference for JiT I suppose.
Have the same result but trying to scale to zero, because i think the idea it's that the instances die as fast as possible. I'm having some issues but in GCP connections; in performance we solve it by let each instance live about 5 to 10 minutes
"Not least of which"? WTH is that?
graalvm cannot be trusted , you can end up with coruppted binary. example: objectmapper.wrireObjectAsString will return empty string when compiled to native image