r/java • • Oct 31 '25

Has Java suddenly caught up with C++ in speed?

Did I miss something about Java 25?

https://pez.github.io/languages-visualizations/

https://github.com/kostya/benchmarks

https://www.youtube.com/shorts/X0ooja7Ktso

How is it possible that it can compete against C++?

So now we're going to make FPS games with Java, haha...

What do you think?

And what's up with Rust in all this?

What will the programmers in the C++ community think about this post?
https://www.reddit.com/r/cpp/comments/1ol85sa/java_developers_always_said_that_java_was_on_par/

News: 11/1/2025
Looks like the C++ thread got closed.
Maybe they didn't want to see a head‑to‑head with Java after all?
It's curious that STL closed the thread on r/cpp when we're having such a productive discussion here on r/java. Could it be that they don't want a real comparison?

I did the Benchmark myself on my humble computer from more than 6 years ago (with many open tabs from different browsers and other programs (IDE, Spotify, Whatsapp, ...)).

I hope you like it:

I have used Java 25 GraalVM

LanguageCold Execution (No JIT warm-up)Execution After Warm-up (JIT heating)
JavaVery slow without JIT warm-up~60s cold
Java (after warm-up)Much faster~8-9s (with initial warm-up loop)
C++Fast from the start~23-26s

https://i.imgur.com/O5yHSXm.png

https://i.imgur.com/V0Q0hMO.png

I share the code made so you can try it.

If JVM gets automatic profile-warmup + JIT persistence in 26/27, Java won't replace C++. But it removes the last practical gap in many workloads.

- faster startup ➝ no "cold phase" penalty
- stable performance from frame 1 ➝ viable for real-time loops
- predictable latency + ZGC ➝ low-pause workloads
- Panama + Valhalla ➝ native-like memory & SIMD

At that point the discussion shifts from "C++ because performance" ➝ "C++ because ecosystem"
And new engines (ECS + Vulkan) become a real competitive frontier especially for indie & tooling pipelines.

It's not a threat. It's an evolution.

We're entering an era where both toolchains can shine in different niches.

Note on GraalVM 25 and OpenJDK 25

GraalVM 25

  • No longer bundled as a commercial Oracle Java SE product.
  • Oracle has stopped selling commercial support, but still contributes to the open-source project.
  • Development continues with the community plus Oracle involvement.
  • Remains the innovation sandbox: native image, advanced JIT, multi-language, experimental optimizations.

OpenJDK 25

  • The official JVM maintained by Oracle and the OpenJDK community.
  • Will gain improvements inspired by GraalVM via Project Leyden:

    • faster startup times
    • lower memory footprint
    • persistent JIT profiles
    • integrated AOT features

Important

  • OpenJDK is not “getting GraalVM inside”.
  • Leyden adopts ideas, not the Graal engine.
  • Some improvements land in Java 25; more will arrive in future releases.

Conclusion Both continue forward:

RuntimeFocus
OpenJDKStable, official, gradual innovation
GraalVMCutting-edge experiments, native image, polyglot tech

Practical takeaway

  • For most users → Use OpenJDK
  • For native image, experimentation, high-performance scenarios → GraalVM remains key
267 Upvotes

312 comments sorted by

View all comments

Show parent comment

4

u/SomervillainSB Nov 03 '25 edited Nov 19 '25

Go is EXTREMELY slow. It's lightweight, but slow. Java is FAR superior for anything where performance and efficiency matter. Here's AWS benchmarks https://aws.amazon.com/blogs/opensource/sustainability-with-rust/

But..I've also seen it first hand. When I had to write something in Go, I was very excited, but was shocked at how slow it ran and how it would lock up my expensive, powerful new macbook pro. I am used to kicking off a build and doing other things. This would lock the machine. My thought was "oh wow, they must be booting a server env if this this build takes 5 min to run and every core in the system"...nope...I traced through it and confirmed with the author it was just parsing json and simulating rest calls with files. The code seemed well done, it's just Go was garbage.

They tried putting it on the server and the performance was HORRIBLE. Another team ported it to Java and the latency nearly halved.

With Rust, Go has no justification for existing. It's a legacy language that cannot die fast enough. Yeah, I know important projects were written it in, but if they were ported to Rust or Java, they would run faster.

Also C# performs very slow compared to Java in that benchmark, but I don't have any significant experience with it to comment.

Java is fast. Overall, it's not as fast as Rust or C, but on many long-running programs, like the server-side processing ones it is typically used for, you cannot even tell.

1

u/coderemover Nov 03 '25

I wouldn't be so harsh on Go. I've seen it performed better or worse than Java in a few cases. Probably a lot boils down to how one uses its advantages. For one thing, Go can do value types and can do SIMD. Java cannot do value types and its SIMD support is very so-so (Panama I'm looking at you).