You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing an RPC system, I encountered performance issues with the 'get' and 'queueable' APIs. The main problem is that the 'get' API recreates connections for each request, which leads to significant latency overhead, especially in multi-topic scenarios. This connection recreation becomes a bottleneck when handling multiple topics simultaneously.
The text was updated successfully, but these errors were encountered:
Querier to get is a bit like Publisher to put. When you first declare querier, zenoh will perform certain protocol-level optimizations to improve performance of subsequent z_querier_get calls (+ allow checking for matching queryables), that is why I expect it to have an impact on performance in your case.
Describe the feature
When implementing an RPC system, I encountered performance issues with the 'get' and 'queueable' APIs. The main problem is that the 'get' API recreates connections for each request, which leads to significant latency overhead, especially in multi-topic scenarios. This connection recreation becomes a bottleneck when handling multiple topics simultaneously.
The text was updated successfully, but these errors were encountered: