You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grp...@googlegroups.com
Hi,
It looks like grpc-core performs a deduplication of TCP connections
for subchannels with the same channel arguments [1]. However it
doesn't look like it's a case for grpc-go implementation.
It sounds like a useful behavior in the context of grpclb, as it
allows reducing number of connections to the remote balancer (as
multiple channels can point to the same remote balancer server).
Is it just a missing functionality at grpc-go side or some fundamental
difference in implementations?
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grpc.io
I'd need to learn more about the C implementation of connection deduplication before deciding whether it makes sense for grpc-go. E.g.s: Is it optional or always enabled? Does it scale connections when the maximum streams limit is reached?
Could you file a bug against grpc-go for this if you think it's worth investigating further?