mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
20 lines
1.5 KiB
Plaintext
20 lines
1.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/optimization/optimizing-networking.adoc
|
|
|
|
[id="optimizing-mtu_{context}"]
|
|
= Optimizing the MTU for your network
|
|
|
|
There are two important maximum transmission units (MTUs): the network interface controller (NIC) MTU and the cluster network MTU.
|
|
|
|
The NIC MTU is only configured at the time of {product-title} installation. The MTU must be less than or equal to the maximum supported value of the NIC of your network. If you are optimizing for throughput, choose the largest possible value. If you are optimizing for lowest latency, choose a lower value.
|
|
|
|
The OpenShift SDN network plugin overlay MTU must be less than the NIC MTU by 50 bytes at a minimum. This accounts for the SDN overlay header. So, on a normal ethernet network, this should be set to `1450`. On a jumbo frame ethernet network, this should be set to `8950`. These values should be set automatically by the Cluster Network Operator based on the NIC's configured MTU. Therefore, cluster administrators do not typically update these values. Amazon Web Services (AWS) and bare-metal environments support jumbo frame ethernet networks. This setting will help throughput, especially with transmission control protocol (TCP).
|
|
|
|
For OVN and Geneve, the MTU must be less than the NIC MTU by 100 bytes at a minimum.
|
|
|
|
[NOTE]
|
|
====
|
|
This 50 byte overlay header is relevant to the OpenShift SDN network plugin. Other SDN solutions might require the value to be more or less.
|
|
====
|