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.

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

Network topology awareness #669

Open
phillebaba opened this issue Dec 17, 2024 · 0 comments
Open

Network topology awareness #669

phillebaba opened this issue Dec 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@phillebaba
Copy link
Member

phillebaba commented Dec 17, 2024

Describe the problem to be solved

When doing lookups in the DHT the first peer found will be returned. The query does not take into consideration the network topology of the Kuberentes cluster. Most cloud providers have multiple zones per region. Network traffic within the same zone is usually faster and cheaper compared to cross zone traffic. Spegel should prioritize peers in the same zone over other peers when possible.

Proposed solution to the problem

There has been some interesting research already done on the topic about partitioning.

https://research.protocol.ai/publications/enriching-kademlia-by-partitioning/monteiro2022.pdf

We need to decide on the best solution to partition the DHT to avoid added latency for lookups.

Relates to #551 and #530

@phillebaba phillebaba added the enhancement New feature or request label Dec 17, 2024
@phillebaba phillebaba moved this to Todo in Roadmap Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant