LIlichtenberger·Dec 20, 2025Submission
(Generational) Shenandoah GC (Low Latency) Support in GraalVM Native Images
1 points · Open discussionoracle
graal
Java2016–2026
oracle / graal
graal
GraalVM compiles applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
94Distinct people
146Mentions
2Explicit recommenders
21.8KGitHub stars
What to know before exploring
What it is
GraalVM compiles applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
"I love the promise of Graal native binaries. At the moment I'm unable to get it to work with my codebase." [2] "Building is a resource hog. I set up a VM with 2 CPUs, 100GB of…
Mawr used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- babashka/babashka · linked in 3 of the same discussions
- openjdk/jdk · linked in 2 of the same discussions
- oracle/graaljs · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year146 dated mentions
Observed mentions: 2016-07-08 13:46:19 UTC to 2026-10-02 12:57:29 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 12 | 5 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 32 | 4 | 28 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 24 | 3 | 21 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 15 | 1 | 14 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 19 | 3 | 16 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 11 | 1 | 10 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 5 | 1 | 4 |
What Hacker News says
10 sourcesBTW: We (the GraalVM team) maintain a full-blown LLVM bitcode runtime that can be embedded in Spring or any other JVM application and compiled to native: https://github.com/oracle/graal/tree/master/sulong
In Java Hello World, LLVM EditionTruffle is not part of OpenJDK. It's a separate project and licensed under the Universal Permissive License: https://github.com/oracle/graal/tree/master/truffle.
The UPL is an OSI-approved open source license. It shouldn't be a problem to use in any setting, but you should check with your legal team to see what licenses are approved.
In Java 25 officially released> All JavaScript regexes engines that we could find, except one,
use a backtracking implementation strategy [Chromium 2009;
DukTape 2013; Hermes 2022; MuJS 2014; QuickJS 2020; WebKit 2018].
The exception is V8...
Well, maybe there's another: TRegex [1] in GraalJs [2].
[1] https://github.com/oracle/graal/tree/master/regex / https://epub.jku.at/urn:nbn:at:at-ubl:1-24940
[2] https://github.com/oracle/graaljs
In Linear Matching of JavaScript Regular ExpressionsProject Crema – Open World for Graal Native Image
3 points · Open discussionNot sure why people always say it's so hard to build GraalVM ... all you need is roughly 2 prerequisites and one build command. The prerequisites are a "Labs JDK" which is essentially a slightly modified OpenJDK with more up to date JVMCI (the JIT interface used by Graal) and the build tool "mx".
Since you want to build completely from source, you start by installing OpenJDK. Then you clone the Labs JDK repo [0] and build it just like how you would build any other OpenJDK. Once you have the Labs JDK, you don't need the OpenJDK anymore, since that's only necessary to build the Labs JDK. If you use a normal OpenJDK instead of Labs JDK for Graal, the Graal build will most likely tell you something about "too old JVMCI" and fail. Don't do that.
Next you clone mx [1] and graal [2] into some folder and add the mx folder to PATH. You also need P
Read the rest
ython and Ninja installed, and maybe something else which I can't remember anymore (but you'd quickly figure it out if the build fails). Once you have that, you go to graal/vm and run the relevant "mx build" command. You specify the path to the Labs JDK via the "--java-home" CLI option and you have to decide which components to include by adding them to the build command line. I can't remember what exactly happens with just "mx build" but chances are this only gives you a bare GraalVM without anything else, which means also no SubstrateVM ("native-image"). By adding projects on the command line, you can include whatever languages/features are available. And that's it. After some time (depending on how beefy your computer is), you get the final GraalVM distribution in some folder, with a nice symlink to find it.
It's not exactly documented in a good way, but you can figure it out from the CI scripts which are in the git repos of Graal and Labs JDK. The "mx build" command is where you decide which languages and features to include; if you want to include languages from external repositories, you have to clone them next to the graal and mx folder and add the relevant projects to the mx build command.
[0] https://github.com/graalvm/labs-openjdk
[1] https://github.com/graalvm/mx
[2] https://github.com/oracle/graal
No backreference support in the state machine, disappointing https://github.com/oracle/graal/blob/master/regex/README.md
In Matching Regexps 200 Times FasterHow does it compare to graal wasm? https://github.com/oracle/graal/blob/master/wasm/README.md/
In Chicory: A JVM native WebAssembly runtimeSorry, I know you weren't asking me, but for this same use case, yes, I've used a GHA build matrix with each OS/arch pair.
Cosmo/APE support would fix this, and GraalVM already ships with a Musl libc implementation, so it isn't very far off.
https://github.com/oracle/graal/issues/8350
In Compiling Java into native binaries with Graal and Millhttps://github.com/oracle/graal/issues/8350
Plz upvote
In Compiling Java into native binaries with Graal and Mill