On Wed, Oct 17, 2018 at 5:04 PM wrote:
> Hi Josh,
>
> Thanks for getting back ! Wouldn't having a single TCP connection be a
> bottleneck (assuming no layer-4 load balancer) especially if there is a
> slow reader, tcp flow control would limit other streams on that connection.
> In that case would
Hi Josh,
Thanks for getting back ! Wouldn't having a single TCP connection be a
bottleneck (assuming no layer-4 load balancer) especially if there is a
slow reader, tcp flow control would limit other streams on that connection.
In that case wouldn't having more connections help ?
Thanks,
Nakul
*+grpc...@googlegroups.com *
*moving golang-nuts@googlegroups.com to BCC*
In general, connections are not cheap, but stubs are. Actual
implementations for some languages differ, but Go complies with this.
What that means is that, generally speaking, you should not try creating
the *grpc.ClientC
Hello,
I intend to use grpc between two fixed endpoints (client and server) where
the client receives multiple requests (the client serves as a proxy) which
in turn sends a grpc request to the server. I wanted to know of the
following would be considered good practice:
a) For every request tha
