Feature/latency based gateway selection #3081
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jstuczyn
requested review from
durch,
futurechimp,
neacsu and
octol
as code owners
jstuczyn
force-pushed
the
feature/latency-based-gateway-selection
branch
from
4dca33d
to
3bb0500
Compare
I know, I should have probably included them properly during rebasing ¯\_(ツ)_/¯
jstuczyn
force-pushed
the
feature/latency-based-gateway-selection
branch
from
d206e47
to
eb27b37
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Doesn't really close any ticket in particular but is a first step towards #3070
This PR introduces new optional mechanism for choosing gateways. Rather than selecting one uniformly, it's now possible to select it weighted by inverse latency. Currently this option is enabled for
nativeandsocks5clients with the--latency-based-selectioninitflag.