feat(p2P): Add new whitelist policy #1544
Open
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
Member
Author
|
Replaces: #1269 |
|
Bencher Report| Branch | feat/new-whitelist-policy |
| Testbed | ubuntu-22.04 |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result minutes (m) (Result Δ%) | Lower Boundary minutes (m) (Limit %) | Upper Boundary minutes (m) (Limit %) |
|---|---|---|---|---|
| sync-v2 (up to 20000 blocks) | 📈 view plot 🚷 view threshold | 1.71 m(-0.10%)Baseline: 1.71 m | 1.54 m (90.09%) | 2.06 m (83.25%) |
msbrogli
force-pushed
the
feat/new-whitelist-policy
branch
from
a414e74 to
812f883
Compare
msbrogli
force-pushed
the
feat/new-whitelist-policy
branch
4 times, most recently
from
d165bef to
df4d9d6
Compare
Co-Author: LFRezende <[email protected]>
msbrogli
force-pushed
the
feat/new-whitelist-policy
branch
from
df4d9d6 to
e5c9d1b
Compare
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.
Co-Author: LFRezende [email protected]
Motivation
What was the motivation for the changes in this PR?
Acceptance Criteria
Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged