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

Determine best proxy #907

Closed
crioto opened this issue Apr 30, 2018 · 2 comments
Closed

Determine best proxy #907

crioto opened this issue Apr 30, 2018 · 2 comments
Assignees
@crioto
Labels
complex enhancement

Comments

@crioto
Copy link
Member

crioto commented Apr 30, 2018

Instead of using all possible proxies we need to determine one single proxy that have better connection quality (less latency value). For this purpose daemon will keep list of all known proxies and use ICMP to determine latency value of each. When instance requests proxies it will just use the best one (or maybe two as a backup)
@crioto crioto self-assigned this Apr 30, 2018
@crioto crioto added this to the v.7.2.0 milestone Jul 30, 2018
@kurmanbekova6
Copy link

Proxies: 85.25.210.145:40622/20004 [108] 85.93.89.182:40622/20027 [108]
Fixed in Master

@crioto crioto removed this from the v7.2.0 milestone Nov 23, 2018
@kurmanbekova6
Copy link

Proxies: 85.93.91.135:40622/20125 [96]
Tested in prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crioto crioto

Labels
complex enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crioto @kurmanbekova6