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 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.
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
The text was updated successfully, but these errors were encountered: