GraalVM CE can now sandbox untrusted JavaScript and WebAssembly code! ๐
As AI generates more and more of the code we run, the ability to execute it safely matters more than ever.
We have more coming that builds on this, so stay tuned!
https://t.co/gLPTiqxLrH
GraalWasm just got faster! ๐ฅ
The new threaded interpreter delivers significantly better interpreter performance. In interpreter benchmarks, total execution time is reduced by 5-40%!
Details: https://t.co/PbzZhFodIW
Excited to speak at #WasmCon Europe next Monday about bringing #WebAssembly to the JVM ecosystem with @GraalVM.
Iโll demo GraalWasm in a Spring Boot app and show how GraalVM can compile JVM apps to Wasm for browser, mobile, and cloud. Join us!
Details: https://t.co/IVf9IU2oJD
@ARCaputo3@alina_yurenko@graalvm AWT works in native images on Linux and Windows, but requires additional app-specific reachability metadata, at least currently. The easiest way to get started is to run your tests with the tracing agent to collect this metadata: https://t.co/xFE3uwSod5
@KiyayYippee@alina_yurenko@graalvm Sure, newer versions of Spring MVC come with out-of-the-box support for @GraalVM. Just compile your app with GraalVM and you should be good to go. :)
@brunoborges@starbuxman Would be interesting to include a @GraalVM-compiled version of the Spring app in the comparison. Could get memory usage much closer to Go without sacrificing latency and throughput.
GraalVM in action: wouldn't it be cool to move your workload from using 43 replicas to 12, and CPU cores from 15 to 5, reducing resources usage by ~67%? You can do so with @GraalVM Native Image!
Good morning #JFokus!๐
Make sure to catch @shaunmsmith and @fniephaus to ask anything you want to know about GraalVM & WebAssembly, and attend their session on Wednesday!
GraalVM 25.0.2 is now available! ๐
Upgrade to get the latest security updates and improvements.
Release notes: https://t.co/2NFJMafkUa
Downloads: https://t.co/ueQ1ZUwV0j
@thomaswue@parttimen3rd@graalvm Turns out our handling for `--version`, `--help`, and `--help-extra` in the `native-image` launcher was unnecessarily slow, but that was relatively easy to fix: https://t.co/NfYIfMceho
GraalVM Native Image is ~3.5x faster than SapMachineโฆ ๐
โฆ in @parttimen3rd's version string benchmark.
Why? The `native-image` launcher is a native image itself. So it starts up much faster, and uses fewer CPU and memory resources!
PR with details: https://t.co/NfYIfMbGrQ
GraalVM Native Image is ~3.5x faster than SapMachineโฆ ๐
โฆ in @parttimen3rd's version string benchmark.
Why? The `native-image` launcher is a native image itself. So it starts up much faster, and uses fewer CPU and memory resources!
PR with details: https://t.co/NfYIfMbGrQ
@parttimen3rd@thomaswue@graalvm Makes sense. GraalVM is slightly slower because it not only enables JVMCI, it also uses it to install the Graal compiler.
WasmGC is coming to GraalWasm, unlocking the power of JVM garbage collectors for #WebAssembly! This will also get GraalWasm a lot closer to implementing the full Wasm 3.0 spec.
Join @shaunmsmith and me at @Jfokus next month to learn more: https://t.co/8Xrk5mlY7V
"GraalVM: Database Integration, Serverless Innovation and the Future" an https://t.co/84MwkKXqXl conversation with @thomaswue about GraalVM release changes, database integration and serverless architectures
is ready to listen https://t.co/qOaXA4kvCj #airhacks#java#podcast