-
Notifications
You must be signed in to change notification settings - Fork 224
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
Support for different relay selection strategies #2917
Comments
Another idea that has been floated internally was to have relays be aware of their current load, and if exceeding a threshold, redirect clients to another node. That said, this may require some coordination between relays. |
Is this feature considered for implementation? If yes, I already have some work on a decentralized relay network that I would like to contribute. |
@giangndm It's currently not high enough priority that it's made it onto our roadmap yet. But that doesn't mean it's not an interesting thing we don't want. Feel free to share your ideas or implementation here. |
@flub Sure, I will draft an idea about relay's network. |
It would be nice to be able to customize the relay selection strategy. For example, to randomly select from the best n by latency rather than just the single one with lowest latency.
This would be useful when running many smaller-capacity relays to ensure clients are distributed (somewhat) evenly across them rather than overloading a single one
The text was updated successfully, but these errors were encountered: