Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Provide a connection pool #17

Closed
nytopop opened this issue May 27, 2020 · 0 comments
Closed

Provide a connection pool #17

nytopop opened this issue May 27, 2020 · 0 comments
Labels
enhancement New feature or request performance

Comments

@nytopop
Copy link
Owner

nytopop commented May 27, 2020

As it stands, services need to manage peer connections manually (and can't share them with each other), which introduces extra latency / overhead.

Instead, there should be a pool of connections in MultiNodeCut that all services have access to.

This will probably involve implementing some kind of lazy connection type, as one isn't provided natively by tonic.

Related: hyperium/tonic#167
@nytopop nytopop added enhancement New feature or request performance labels May 27, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
enhancement New feature or request performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nytopop