Based on the preceding calculations, the following table provides additional examples of the amount of data that is sent per Ethernet frame for standard and jumbo frames.
Table 10. Data payload to Ethernet frame percentage
Packet type | Data to Ethernet frame percentage | |
Standard frame | Jumbo frame | |
IPv4 / TCP | 94.93% | 99.14% |
IPv4 / TCP / Linux Timestamp | 94.15% | 99.00% |
IPv4 / TCP / Linux Timestamp / VLAN | 93.90% | 98.96% |
IPv6 / TCP | 93.63% | 98.92% |
IPv6 / TCP / Linux Timestamp | 92.85% | 98.78% |
IPv6 / TCP / Linux Timestamp / VLAN | 92.59% | 98.74% |
IPv4 / UDP | 95.71% | 99.27% |
IPv4 / UDP / Linux Timestamp | 94.93% | 99.14% |
IPv4 / UDP / Linux Timestamp / VLAN | 94.67% | 99.09% |
IPv6 / UDP | 94.41% | 99.05% |
IPv6 / UDP / Linux Timestamp | 93.63% | 98.92% |
IPv6 / UDP / Linux Timestamp / VLAN | 93.37% | 98.87% |
Note: NFS v2 is UDP. NFS v3 and v4 are TCP. SMB is TCP.
As shown in the preceding table, jumbo frames deliver between 98 and 99 percent efficiency depending on the packet type. The efficiencies are only maximized when all hops from the client endpoint to a PowerScale node support jumbo frames. Otherwise, packets might be fragmented, leading to additional processing overhead on devices or PMTUD finding the lowest MTU along the path. Therefore, jumbo frames are recommended for optimal performance. However, each workload environment is unique. Measure performance enhancements in a lab before updating a production network.