On machines that are within the same network, you can expect latencies in the low hundreds of microseconds. I have personally measured numbers within 100 - 200 microseconds on nearby machines. I had to tune the server somewhat to achieve this, but it is possible.
On Tuesday, August 9, 2016 at 10:33:31 AM UTC-7, Pradeep Singh wrote: > > Oh I was running the included benchmark in gRPC src code. > I think it reuses the same connection. > > 300us sounds really good. > > What latency do you guys notice when client and server are running on > different hosts? > > Thanks, > > On Tue, Aug 9, 2016 at 8:58 AM, Eric Anderson <[email protected] > <javascript:>> wrote: > >> On Mon, Aug 8, 2016 at 12:35 AM, <[email protected] <javascript:>> wrote: >> >>> With custom zmq messaging bus we get latency in order of microseconds >>> between 2 services on same host (21 us avg) vs 2 ms avg for gRPC. >>> >> >> Did you reuse the ClientConn between RPCs? >> >> In our performance tests on GCE (using not very special machines, where >> netperf takes ~100µs) we see ~300µs latency for unary and ~225µs latency >> for streaming in Go. >> > > > > -- > Pradeep Singh > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/b1296fb1-3117-40d3-8ac0-be71180c17c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
