Hi, We have a gRPC streaming server and it serves only one streaming RPC but there are lots of data that has to be streamed using this RPC. And our customer is ready to invoke this RPC only once (they are not ok to have multiple streaming calls running). We hit a throughput issue and we observed that by increasing the HTTP/2 window size from its default 64K, we are able to achieve more throughput.
However I would like to know with default value of 64K window size how can we achieve more throughput. Is there a way to tell the gRPC stack to use multiple streams per streaming RPC? So instead of using one stream with larger window, it can create and use multiple small streams of 64K window by dynamically creating a stream whenever it senses the existing active streams are choked. If not, what other options do we have to increase the throughput with default window of 64K? Thanks, Vivek -- 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]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/51d7b69c-2e81-4cd6-95c2-dea90510f31c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
