grpc_bench

They are, but not so much in the case of Go - it is optimized for small containers with few CPU cores, that do not need to sustain (inevitable) high allocation throughput. This is what happens when it's in different conditions, in a test that is still very friendly to Go using the stack which it's supposed to be very strong at: https://github.com/LesnyRumcajs/grpc_bench/discussions/441 Note the CPU % usage. The numbers only get more interesting once you start using 64 core hosts. You could also look at write barrier/synchronization/allocation sensitive microbenchmark instead which paints way less positive picture: https://benchmarksgame-team.pages.debian.net/benchmarksgame/... (special props to OpenJDK's write barrier elision, this is something .NET needs to do better at still)

Go's GC wasn't really made with throughput maximization in mind. It's a language that doesn't scale that well to take advantage of beefy nodes and has weak compiler. I suppose the Google's vision for it is to "crank the replica count up". gRPC servers based on top of ASP.NET Core, Java Vert.X and Rust Thruster will provide you with much higher throughput on multi-core nodes. https://github.com/LesnyRumcajs/grpc_bench/discussions/441

Also worth checking out the gRPC benchmarks: https://github.com/LesnyRumcajs/grpc_bench/discussions/284 dotnet is up there with Rust.

Jeff's reply needs no addendum. But as for some background: I am a PM for Microsoft Build of OpenJDK and from late last year to around May this year I made contributions to the gRPC_bench repo as a Microsoft employee for some experiments we have been working on, to evaluate and improve different ways of implementing gRPC exchange in Java. [1] This fork was intended for newer experiments, one of them being about coding and running these benchmarks on GitHub Codespaces. For that, I needed the repo on an org where we, as employees, have Codespaces enabled. The rest is HN history (back to Jeff's reply above [2]). Merry Christmas all! [1] https://github.com/LesnyRumcajs/grpc_bench/commits?author=br... [2] https://news.ycombinator.com/item?id=29685628

Great article. The JVM is one of the most astonishing pieces of software ever created. I was looking at gRPC benchmarks the other day (https://github.com/LesnyRumcajs/grpc_bench/wiki/2021-08-30-b...) and 6 of the top 7 performing gRPC implementations on 3 core CPUS were on the JVM.

Comments from one of the maintainers on why Java is on top https://www.reddit.com/r/grpc/comments/muy8dj/grpc_bench_ope... Small clarification (to my understanding, I'm not a Java Guru) on why Java got on top - those Java implementations use something called Direct Executor. It's super performant when there's no chance of a blocking operation. But if you are to do anything more than echo service, you might be in trouble. Other implementations probably don't suffer from the same constraint PR and discussions here- https://github.com/LesnyRumcajs/grpc_bench/pull/91

For comparison: https://github.com/LesnyRumcajs/grpc_bench/blob/master/kotli... https://github.com/LesnyRumcajs/grpc_bench/blob/master/java_... Looking at the build files, different versions of the libraries appears to be used. The Java implementation is configurable but defaults to something called "direct executor". Maybe that explains the difference.

It appears to point to here: https://github.com/LesnyRumcajs/grpc_bench/tree/master/java_...

Follow the code! COPY java_grpc_sgc_bench /app Directory here: https://github.com/LesnyRumcajs/grpc_bench/tree/master/java_...

Where is the source code for the winning Java implementation? Not really anything here: https://github.com/LesnyRumcajs/grpc_bench/tree/master/java_...

> The current results aren't realistic because the method on the server does no work. In the real-world there will be I/O (reading from FS, DB, calling another service, etc) and an execution model that assumes no blocking will grind to a halt. https://github.com/LesnyRumcajs/grpc_bench/issues/120