https://github.com/grpc/grpc-go/issues/524#issuecomment-180536815
Go's http2 server does this aggregation automatically. It has a write
scheduler that only flushes only when a packet is full or there's nothing
else to send.
On Thursday, August 4, 2016 at 11:18:00 AM UTC+8, Yan Yan wrote:
>
> commit 7f6c7798b08afcbf77e675e0bc4e8ce5b6ba580d
> Date: Thu Jul 14 18:10:19 2016 -0700
> route_guide.proto
> rpc ListFeatures(Rectangle) returns (stream Feature) {}
>
> I am running the above version of gRPC python. I have tried throttling the
> server to send 100, 500 or 1000 responses per second. I have found the
> client to receive responses in 4k batches. How can I send them ASAP? Is it
> related to TCP_NODELAY? Does gRPC c++ offer a way to send them ASAP? Is
> there a way to flush earlier? Is there away to adjust the batch size or
> buffer size? Thx.
>
>
--
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/0bc1c8f4-6c4d-438e-bdfb-7a830c56117b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
