Add daemonset that configures TCP receive buffer limit #906
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
…ut does not seem to be working when pulling the script via kubectl.
…prove tail step times in DCN-bound workloads. Also add this command to the existing manual daemonset, for users running old GKE versions.
… DSes so users have more fine grained control
thebinaryone1
approved these changes
Dec 9, 2024
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.
Internal benchmarking of DCN performance indicates that these settings may offer some improvement.
Committing this as a separate DS to give users the option of whether or not they want to apply it in addition to the other settings we already give them (either automatically or via v6e-network-optimization.yaml if they use an old GKE version).