grpc_bench
gRPC
grpc_bench | gRPC | |
---|---|---|
58 | 11 | |
850 | 11,171 | |
- | 0.5% | |
8.4 | 9.6 | |
about 15 hours ago | 6 days ago | |
Dockerfile | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
grpc_bench
-
Poor gRPC performance on test - help needed
SayHello, GetUser, and Sum differ only by payload size. Sum is the simplest one - (int, int) -> int, GetUser is (long) -> User (medium payload), and SayHello uses exactly the same payload as this test: https://github.com/LesnyRumcajs/grpc_bench/tree/master/dotnet_grpc_bench
-
2023-06-25 gRPC benchmark results
This is correct. The problem is not with the benchmark itself but with the implementation. If you look at the result, you can see that even with 6 "allowed" CPUs, the vertx server utilizes less than 100%. Apparently, the current vertx implementation (the one implemented in https://github.com/LesnyRumcajs/grpc_bench/tree/master/java_vertx_grpc_bench) is single-threaded or has some other limitation.
Another iteration of grpc_bench!
-
Why does C#/.NET is in demand in Philippines especially in BGC? How about PHP?
Because it's fast and runs on Windows, Linux, and MacOS
- .NET Core performance on Linux
-
Another two cents about the current situation with the Scala user base and economics.
In general though, akka/pekko-streams are known to be one of the fastest implementations out there. Their grpc client for example even beats languages like Rust (see https://www.lightbend.com/blog/akka-grpc-update-delivers-1200-percent-performance-improvement and https://github.com/LesnyRumcajs/grpc_bench/wiki/2022-03-15-bench-results).
-
What is the current status of Akka in your organisation?
The whole point I was making is at least up until 8 months ago (at best, I can't commend on the stability/maturity/performance of shardcake) Akka was the only mature library/ecosystem solving this problem with also a very strong focus on performance (for example still to this day, akka/pekko-grpc is generally one of the fastest grpc implementations I am aware of, its even beating rust if you have at least 2 cores (see https://github.com/LesnyRumcajs/grpc_bench/wiki/2022-03-15-bench-results)
-
QuickBuffers 1.1 released
It would be interesting to create a new java benchmark with your implementation.
-
Ask HN: Examples of Top C# Code?
Also worth checking out the gRPC benchmarks: https://github.com/LesnyRumcajs/grpc_bench/discussions/284
dotnet is up there with Rust.
gRPC
- FLaNK Stack Weekly 12 February 2024
-
Reference Count, Don't Garbage Collect
That's not true at all. Case in point In general, this is not a problem that AGC can solve. The language can help (something Java is admittedly particularly bad at) but even so, there'll always be avenues for leaks. That's just the nature of shared things. Interestingly, in the linked grpc case, the leaked memory is only half the problem -- AGC doesn't help at all with the leaked HTTP2 connection.
-
Distroless Alpine
I've trialled my new image with an existing project via JLink that's heavy on Netty and gRPC the image works great (with a small tweak to exclude grpc-netty-shaded due to grpc-java#9083).
-
What are the user agents?
When developing an application, the vast majority of code is written by other people. We import that code and make use of it to get whatever we need done. In this case, the developer of an various android applications are using grpc-java.
-
Buf raises $93M to deprecate REST/JSON
`proto_library` for building the `.bin` file from protos works great. Generating stubs/messages for "all" languages does not. Each language does not want to implement gRPC rules, the gRPC team does not want to implement rules for each language. Sort of a deadlock situation. For example:
- C++: https://github.com/grpc/grpc/blob/master/bazel/cc_grpc_libra...
- Python: https://github.com/grpc/grpc/blob/master/bazel/python_rules....
- ObjC: https://github.com/grpc/grpc/blob/master/bazel/objc_grpc_lib...
- Java: https://github.com/grpc/grpc-java/blob/master/java_grpc_libr...
- Go (different semantics than all of the other): https://github.com/bazelbuild/rules_go/blob/master/proto/def...
But there's also no real cohesion within the community. The biggest effort to date has been in https://github.com/stackb/rules_proto which integrates with gazelle.
tl;dr: Low alignment results in diverging implementations that are complicated to understand for newcomers. Buff's approach is much more appealing as it's a "this is the one way to do the right thing" and having it just work by detecting `proto_library` and doing all of the linting/registry stuff automagically in CI would be fantastic.
-
grpc_bench: open-source, objective gRPC benchmark
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. The related discussion can be found in this PR.
-
Android Java GRPC Tutorial
clone https://github.com/grpc/grpc-java
-
GRPC
If you do streaming then the best option would be to use a so called manual flow control. You can find an example here.
-
High performing APIs with gRPC
Another interesting link is their official grpc-java benchmarks project, which is also used in the benchmark I've posted you.
-
Java 16 EA Alpine & JLink vs Graal
Both JLink (gRPC#3522) and Graal have some issues; I'm especially concerned about the Serial GC in Graal so will be putting that under some stress soon to see if that confirms my suspicions. I'll also be good when some Java 16 JRE Alpine images appear as the JDK is too bloaty.
What are some alternatives?
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
Dubbo - The java implementation of Apache Dubbo. An RPC and microservice framework.
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
Netty - Netty project - an event-driven asynchronous network application framework
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
Finagle - A fault tolerant, protocol-agnostic RPC system
greeter-bpf - implementing gRPC GreeterServer in eBPF just for fun.
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
ghz - Simple gRPC benchmarking and load testing tool
Undertow - High performance non-blocking webserver
grpc_bench - Various gRPC benchmarks
KryoNet - TCP/UDP client/server library for Java, based on Kryo