-
Notifications
You must be signed in to change notification settings - Fork 569
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
[10] Sophisticated ping strategy and background pinging #1901
Comments
Great strategy. |
Great idea @sschiessl-bcp. I recently posted BitShares Network Map #bitshares-core/1348 which may be considered to visualize the connections the client is discovering/connecting to/excluding/etc. May also be display info about each node on the map. |
I will re-evaluate background pinging when doing this task (see #1940) |
How is work progressing on this? I'm looking forward to your work on background pinging as well |
This is done, just not tested well enough due to delays. Will come soon. Background pinging also works nicely, but will require UX and not within scope of this issue. |
I included the background pinging and increased the estimate, will adjust when done. Done so far
Outstanding:
|
Done now. Hours have been updated, please adjust if not acceptable. |
I have included a better UX for background pinging, took 1,5h more, including testing. Please adjust or discuss. I will not include user node management and have moved it to follow up issue to be able to include it in this staging release. |
Closes #1901 Sophisticated ping strategy
Ping Strategy
The first step for the new ping strategy was completed with #1521
In the next step I propose to do a binary-tree like ping strategy.
The ping strategy stops when a sufficiently fast node has been found. If first iteration is not successfull, all nodes are pinged until a sufficiently fast one is found. In the next ping cycle the old region / country is remembered to accelerate pinging.
Background pinging
In order to achieve this it must be able to manually show the node list even if auto select is one.
The text was updated successfully, but these errors were encountered: