Repository navigation
add separate discovery interval to stitch-p2p swarm - #35
Merged
Merged
Conversation
This file contains hidden or 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
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.
The Swarm's connect loop polled the broker for peers at the sync pull interval, so a short pull interval (200 ms in c2-fusion) also meant five broker queries per second. Adds
Swarm::spawn_with_discovery_interval(peer, node, pull, discovery);Swarm::spawndelegates with discovery equal to pull, so existing callers are unchanged. stitch-p2p 0.1.1. The broker test now runs both entry points against a real mqdb (the new case uses a 3 s discovery interval).