Define TCP max window 16MB #129
Draft
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
pschork
force-pushed
the
pschork/tcp_max_window
branch
2 times, most recently
from
46d9aa2 to
8f37de6
Compare
pschork
force-pushed
the
pschork/tcp_max_window
branch
from
8f37de6 to
8de7120
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.
Experimental TCP max window settings
You can determine current TCP window setting via
This output show
6.2MBmax windowAccording to https://www.ibm.com/docs/en/linux-on-systems?topic=tuning-tcpip-ipv4-settings#wkvm_tune_tcpip__title__7 10G nic should be able to handle 16MB max window (or more)
To change
tcp_rmemoutside of docker, runsudo sysctl -w net.ipv4.tcp_rmem='4096 131072 16000000'These values are not hard enforced and the kernel might choose something lower.