-
Notifications
You must be signed in to change notification settings - Fork 648
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
litep2p/kad: Configure periodic network bootstrap for better throughput #4942
Open
lexnv
wants to merge
21
commits into
master
Choose a base branch
from
lexnv/litep2p-aggr-queries
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
a126147
net/litep2p: Update connected peers from network backend sooner
lexnv d9b57ee
net/litep2p: Propagate connected peers to the discovery mechanism
lexnv 3b2c5ac
net/litep2p: Start random walks if under connected peers limit
lexnv b61e973
net/kad: Ensure timer moves forward
lexnv 837f196
net/kad: Keep record of inflight kad queries
lexnv 5610b95
net/kad: Reset kad query timer on failure
lexnv f5aee82
net/kad: Downgrade logs to trace and debug
lexnv 6ac1bff
net/kad: Bound maximum number of queries
lexnv 4983b89
litep2p: Rename num connected peers to num sync peers
lexnv 32c9257
litep2p: Rename function to illustrate sync peers
lexnv 2a6d231
litep2p: Improve comment wrt num_sync_connected
lexnv c71fa9e
litep2p: Extract number of distinct connected peers
lexnv 24bafe3
litep2p: Remove fetch sync peers method
lexnv b6c9901
litep2p: Periodically perform kademlia queries instead if under number
lexnv 7bf91eb
Revert "litep2p: Periodically perform kademlia queries instead if und…
lexnv 5d09d4a
litep2p: Change heuristic to 3 times the required discovery number
lexnv f676446
litep2p/discovery: Fallback to 2x factor for discovery
lexnv 0124309
Merge remote-tracking branch 'origin/master' into lexnv/litep2p-aggr-…
lexnv a8e1cae
discovery: Introduce mandatory query for discovery every 16 minutes
lexnv fa3ce93
litep2p/discovery: Better logs for mandatory queries
lexnv 2ab14ee
litep2p/discovery: Periodic kad queries every 30 minutes
lexnv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if
in_peers
is lower than 15?Do you think the discovery should be guided by the number of sync peers connected, and not by the number of known peers?
Also, I would make sure we do a random walk at least once per minute as it was before, even if we have enough peers connected (make
discovery_only_if_under_num
slow down queries, but not stop them completely).