TCP Transport: enable NO_DELAY for clients #822
Merged
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.
requires status-im/nim-chronos#340
I'm actually pro Naggle and think that delayed acks should get their sh*t together, but TCP_NO_DELAY is a lot easier to enable than TCP_QUICKACK :/
On linux platforms, having it both delayed acks & naggle can cause up to 40ms of unwanted delay
Gossipsub spread speed before / after: (don't mind the different scale on Y axis)
Maybe should be default?