-
Notifications
You must be signed in to change notification settings - Fork 86
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
BlockFetch protocol limit #2624
Conversation
ffb4508
to
f8970b3
Compare
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.
I have a concern as to how this may effect bulk download. Correct me if I'm wrong, but this represents the total data in flight during a bulk block fetch; I assume that we are ack-ing the blocks (probably implicitly by asking for more). This makes it analogous to the role of the TCP congestion window (from a performance perspective). My concern is will 6.4Mb of inflight data be sufficient to hide latency to achieve reasonable throughput for peers that are "reasonably" distant (i.e not in same data centre, but on same continent).
bors merge |
👎 Rejected by too few approved reviews |
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.
lgtm
bors merge |
Build succeeded: |
The block fetch limit is set according to: https://docs.google.com/spreadsheets/d/1W0PJCYPan8smSg_CnuG-fQVFOnb7DzQhm3W1LuVTZR4/edit?pli=1#gid=0