[HN Gopher] GraalVM 22.3: JDK 19 builds, jlink support, new moni...
___________________________________________________________________
GraalVM 22.3: JDK 19 builds, jlink support, new monitoring
features, and more
Author : fniephaus
Score : 24 points
Date : 2022-10-25 16:28 UTC (6 hours ago)
(HTM) web link (medium.com)
(TXT) w3m dump (medium.com)
| ravedave5 wrote:
| Graal seems to be continually almost ready to use, but never
| quite there.
| pjmlp wrote:
| Twitter has been using it in production for ages now.
| metadat wrote:
| What do you mean? I've been using it as the default JVM since
| 2019 or so in both development and production.
|
| My experience has involved zero headaches or serious problems
| due to Graal, and it comes with appreciable performance
| improvements.
|
| One of the more impressive and badass hardcore programming
| language engineering efforts, and still under active
| development right now. It's remarkable technology.
|
| Amazing that it comes from within Oracle, I was surprised.
| Scarbutt wrote:
| _My experience has involved zero headaches_
|
| How? most libs use reflection.
| the-alchemist wrote:
| There's two pieces to GraalVM:
|
| 1. The new JIT
|
| 2. The Native Image, AOT
|
| Reflection is an issue for (2), not (1).
| kasperni wrote:
| GraalVM comes with its own JIT the Graal Compiler [1] which
| I believe was what metadat was talking about. You are
| probably thinking about the native image generation which
| can cause issues with reflection and other dynamic
| constructs.
|
| [1] https://www.graalvm.org/22.3/reference-
| manual/java/compiler/
| cogman10 wrote:
| Reflection only matters if you are using graal for AOT.
| It's still a full JVM.
| fniephaus wrote:
| Also, reflection is supported in AOT mode. The analysis,
| however, does require reachability metadata in some
| cases. In the best case, libraries provide and maintain
| appropriate configuration for this. Reachability metadata
| can also be shared via https://github.com/oracle/graalvm-
| reachability-metadata.
| the-alchemist wrote:
| From what I've noticed, the Clojure community has embraced
| GraalVM the most out of any of the Java community. Babashka,
| think bash+Clojure with built-in JSON+YAML+CSV+REST support, is
| very popular.
|
| https://github.com/babashka/babashka
| Traubenfuchs wrote:
| The upcoming version 3.x.x of Spring Boot, probably the most
| used Java (mostly web) framework comes with first class "native
| image support" using Graal out of the box.
|
| https://spring.io/blog/2022/09/26/native-support-in-spring-b...
| adl wrote:
| Per the GraalVM website: "GraalVM JIT and Native Image will
| become a part of OpenJDK"
|
| I understand the Native Image stuff becoming part of OpenJDK, but
| what does it mean for OpenJDK to get the GraalVM JIT? does it
| replace the one in OpenJDK? will OpenJDK have two JIT
| implementations to choose from?
| the-alchemist wrote:
| Yeah, I bet the GraalVM JIT will be under a flag:
| -XX:EnableGraalJIT or something like that.
| kjeetgill wrote:
| Hotspot introduced the JVM Compiler Interface (JVMCI) a while
| back, so you could drop in any JIT replacement, including
| Graal.
|
| https://openjdk.org/jeps/243
|
| This is different than using GraalVM, which has all the
| polyglot stuff too. And the Native Image AOT stuff is
| different yet again ... I think! There's a lot of uses of the
| same core technology. It's pretty cool stuff!
___________________________________________________________________
(page generated 2022-10-25 23:02 UTC)