-
Notifications
You must be signed in to change notification settings - Fork 134
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
MTU enhancement #205
Comments
@rbankston if we do go down this path, then we need to ensure that we are not including any instance types in the template that do not support jumbo frames: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html |
@detiber indeed. We currently don't include any that aren't available to have jumbo frames. Would allowing the mtu size to be set possibly better going forward? |
@vincepri I'm interested in your thoughts here. I think we want to be able to better optimize for MTU, but we also need to be careful that we don't make it too easy for users to shoot themselves in the foot. |
The MTU is indeed configured at 1500/1440. The process for changing it is documented here and looks pretty straightforward to change the value. |
Describe the solution you'd like
The default MTU within the calico cni provider is for best results when using GCE at 1500. We should update the MTU in this project to match the documentation from Tigera for AWS
Anything else you would like to add:
Updating the MTU helps improve throughput on the cluster.
The text was updated successfully, but these errors were encountered: