We are noticing performance issues when trying to use the bi-directional stream API call to stream data at 2000-4000 updates/second. We enabled debug logging and see that streamId is same for all the outbound and inbound messages.
Question: Does one RPC bi-directional streaming call use only one stream to send data either from client or server? If yes, does that mean, 2000-4000 updates will be sequentially streamed instead of concurrently?
What we tried:
We are using a single bi-directional stream RPC call to publish updates at the rate of 2000-4000 updates/sec
What we did not expect:
Latency issues (~50ms) even when the client and server was running on the same host
Ramachandran Rajagopalan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.