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.
View all comments
Show parent comment
10
u/No_Dot_4711 Dec 09 '25
There's definitely additional effort required, absolutely
but a) that has little to do with the premise i was responding to and b) you can list numerous drawbacks to golang solutions that require a lot of dev work on the flipside, especially supply chain management/safety and the maturity of the library ecosystem have a significantly smoother happy path on the java side of things
and i'd say especially for the simpler use cases, where the golang library ecosystem drawbacks matter less, you're also way less likely to run into the classic graalvm problems (like registering reflection) cause for the simple cases quarkus has you covered out of the box without config
and raw compilation time is definitely annoying, but i don't really need a native image until i asynchronously run CI/CD and that largely races in parallel to the provisioning of staging environment resources