ghz
twitterperf
| ghz | twitterperf | |
|---|---|---|
| 6 | 2 | |
| 2,884 | 62 | |
| - | - | |
| 5.8 | 0.0 | |
| 1 day ago | over 1 year ago | |
| Go | Rust | |
| 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.
ghz
-
Production Twitter on One Machine: 100Gbps NICs and NVMe Are Fast
I once built a quick and dirty load testing tool for a public facing service we built. The tool was pretty simple - something like https://github.com/bojand/ghz but with traffic and data patterns closer to what we expected to see in the real world. We used argo-workflows to generate scale.
One thing which we noticed was that there was a considerable difference in performance characteristics based on how we parallelized the load testing tool (multiple threads, multiple processes, multiple kubernetes pods, pods forced to be distributed across nodes).
I think that when you run non-distrubuted load tests you benefit from bunch of cool things which happen with http2 and Linux (multiplexing, resource sharing etc) which might make applications seem much faster than they would be in the real world.
-
GRPC Performance Testing , Load Testing
I'm not sure. Maybe you can write to the discussion section of the repo https://github.com/bojand/ghz/discussions
-
Testing gRPC services - request collections and modern load testing
In part 1 we looked at ghz for load testing gRPC services, and now I want to cover k6, which claims to be a modern load testing tool built for developer happiness. After only a brief experience with it I can see why is that and why Grafana moved to acquire k6 earlier this year.
-
grpc_bench: open-source, objective gRPC benchmark
It should be unbound, in this particular benchmark we set ghz concurrency to 50 and connections to 5 and we don't set the rps flag of ghz (e.g. --rps=2000, from this tool)
a second container running ghz makes unary requests to the server
twitterperf
-
Production Twitter on One Machine: 100Gbps NICs and NVMe are fast
Thought this was interesting, author provided the source code behind it (rust obviously) https://github.com/trishume/twitterperf.
-
Production Twitter on One Machine: 100Gbps NICs and NVMe Are Fast
Very cool exercise. I enjoyed reading it.
I see a lot of comments here assuming that this proves something about Twitter being inefficient. Before you jump to conclusions, take a look at the author’s code: https://github.com/trishume/twitterperf
Notably absent are things like serving HTTP, not to even mention HTTPS. This was a fun exercise in algorithms, I/O, and benchmarking. It wasn’t actually imitating anything that resembles actual Twitter or even a usable website.
What are some alternatives?
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
quant - QUIC implementation for POSIX and IoT platforms
jmeter-grpc-plugin - A JMeter plugin supports load test gRPC
f-stack - F-Stack is an user space network development kit with high performance based on DPDK, FreeBSD TCP/IP stack and coroutine API.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
k3s - Lightweight Kubernetes
grpc_bench - Various gRPC benchmarks
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
k6 - A modern load testing tool, using Go and JavaScript - https://k6.io
gRPC - The Java gRPC implementation. HTTP/2 based RPC
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
Kreya - Kreya is a GUI client for REST and gRPC with innovative features for environments, authorizations and more.