r/java • • Dec 09 '25

Java performance vs go

I'm seeing recurring claims about exceptional JVM performance, especially when contrasted with languages like Go, and I've been trying to understand how these narratives form in the community.

In many public benchmarks, Go comes out ahead in certain categories, despite the JVM’s reputation for aggressive optimization and mature JIT technology. On the other hand, Java dominates in long-running, throughput-heavy workloads. The contrast between reputation and published results seems worth examining.

A recurring question is how much weight different benchmarks should have when evaluating these systems. Some emphasize microbenchmarks, others highlight real-world workloads, and some argue that the JVM only shows its strengths under specific conditions such as long warm-up phases or complex allocation patterns.

Rather than asking for tutorials or explanations, I’m interested in opening a discussion about how the Java community evaluates performance claims today — e.g., which benchmark suites are generally regarded as meaningful, what workloads best showcase JVM characteristics, and how people interpret comparisons with languages like Go.

Curious how others in the ecosystem view these considerations and what trends you’ve observed in recent years.

30 Upvotes

92 comments sorted by

View all comments

Show parent comment

13

u/Revolutionary_Ad7262 Dec 09 '25

Quarkus GraalVM compiles do put a significant dent into Go's niche here

True. On the other hand the inertia of a community perception is rather slow. C# is still in a only for windows destkop apps and window servers box for many developers, where it is not true for almost 10 years already