Set TCP_NODELAY for sockets #2069
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
During normal operation we send two small messages shortly after one another (chainsync's RequestNext and blockfetch's RequestRange) when we learn of a new block. Without this option we would wait for an ACK of RequestNext before we sent RequestRange.
dcoutts
approved these changes
May 12, 2020
njd42
approved these changes
May 12, 2020
|
bors r+ |
coot
pushed a commit
that referenced
this pull request
May 16, 2022
2069: Set TCP_NODELAY for sockets r=karknu a=karknu During normal operation we send two small messages shortly after one another (chainsync's RequestNext and blockfetch's RequestRange) when we learn of a new block. Without this option we would wait for an ACK of RequestNext before we sent RequestRange. Co-authored-by: Karl Knutsson <karl.knutsson@iohk.io>
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.
During normal operation we send two small messages shortly after one
another (chainsync's RequestNext and blockfetch's RequestRange) when we
learn of a new block.
Without this option we would wait for an ACK of RequestNext before we
sent RequestRange.