Ping p2pool nodes asynchronously #616
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
|
Looks good. Nice improvement |
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.
Sometimes when verification of verthash.dat was done, OCM would have to wait on the last p2pool nodes to respond before a node was selected, and mining could begin.
While #546 improved OCM startup time significantly by pinging the nodes in a go routine, along the rest of the startup processes. This PR allows for p2pool nodes to be pinged asynchronously from each other. Allowing for less time spent waiting for nodes to answer.
Additionally this also changes the default p2pool node. The old p2proxy node no longer exist.