-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
Enable BBR congestion control algorithm #67
Comments
Any desire to explore this, provide some pros/cons/analysis, or draft something and run it for a while on some platforms? Typhoon is non-commercial so it relies on interest like that. As it stands, I probably won't look into this until after the winter holidays or later. |
BBR is a new congestion algorithm released by Google a few months ago. I've been using it in production with no issues that I've seen since then. Here's a technical article on it: The other good pair of articles is:
Enabling it is as simple as setting these values in
|
i feel this kinds (post-boot time configurable) of on host configuration should be configed post k8s installation via on-shot pods on nodes. |
Since this is an additive change, it might be a good use for #140 |
#145 will allow users to provide custom Container Linux Config snippets. The feature will allow users to perform this type of customization, but in an elegant and validated way that merges Container Linux Config snippets into a single declarative Ignition document. Adding files like |
You can now make this and other host customizations using Container Linux Config snippets. These snippets are validated on Its supported on AWS, Google Cloud, and Digital Ocean, with bare-metal coming soon. I don't think you specified your platform? |
This type of customization is provided through Container Linux Config snippets. This is available on cloud platforms today. Track #140 for the feature to be added for bare-metal. |
Feature Request
I'd like to use the BBR congestion control algorithm on my Typhoon deployed cluster. This was enabled in CoreOS itself in coreos/bugs#1719 .
The text was updated successfully, but these errors were encountered: