On 03. 01. 2023. 23:57, 'Sergii Tkachenko' via grpc.io wrote:
Just an idea - did you try to run `ghz` with the `--async` flag. It might make
sense to play around with `--skipFirst` flag as well, so that first request to
not pre-warmed JVM do not bias the result.
Also - looks like REST wrk benchmark uses 400 connections, while gRPC ghz just
one? Consider trying `--connections=400` ghz argument.
Docs: https://ghz.sh/docs/usage
Already did all of that and more:
* played with `--async`, `--concurrency` and `--connections`
* invoked ghz multiple times to make sure server is "warm"
Like I already mentioned, I even wrote my own benchmark that gave *somewhat*
better throughput than ghz, but still way lower than REST tests.
If no one can spot anything I missed on server side, I'll also write my own
benchmarks for REST endpoints - that way I can guarantee that client logic is
the same.
-gkresic.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/dee72ea2-09cc-0a85-eb08-25ec32ae2a4a%40steatoda.com.
