Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

optimise Peer.Routes() for fully connected mesh of node topology #102

Open
murali-reddy opened this issue Feb 4, 2019 · 0 comments · May be fixed by #103
Open

optimise Peer.Routes() for fully connected mesh of node topology #102

murali-reddy opened this issue Feb 4, 2019 · 0 comments · May be fixed by #103

Comments

@murali-reddy
Copy link
Contributor

Routes calculations is order of O(n_peers^2) was optimised in

weaveworks/weave#1773
weaveworks/weave#1761

However for use-cased where mesh of nodes are fully connected i.e) each node is single hop away. Consider this topology as special case when calculating the routes.

This topology is very common in case Kubernetes clusters, and weave-net consuming the mesh library can benefit from this optimised routing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

optimise routes calculation and topology updates for fully connected mesh of node murali-reddy/mesh
1 participant
@murali-reddy