jumbo frames
termnetworking
Ethernet frames carrying more than the standard 1500-byte payload, typically 9000: fewer headers per gigabyte, and misery when one hop in the path disagrees.
The 1500-byte limit is a 1980 economic decision that outlived its reasons; jumbos raise full-frame wire efficiency from about 94.9% to 99.1% and, historically more important, cut per-packet CPU and interrupt work. The catch is agreement: every device in the L2 domain must accept the size, because an MTU mismatch does not degrade politely - it black-holes. That is why jumbos thrive on controlled paths (storage, replication, overlay underlays inside the data center) and die crossing the internet.
Jumbo frames carry more payload per frame than standard Ethernet, which reduces per-packet overhead and CPU interrupts on high-throughput paths. Storage networks and backup traffic are where they earn their keep, and the gain on ordinary mixed traffic is usually negligible.
They fail in a specific and painful way. Every device in the path must agree, and one switch left at the default silently drops the oversized frames, producing a network that passes small packets and pings and fails on real transfers. That symptom looks like an application fault, and it is why the diagnostic is a ping with a large payload and the do-not-fragment flag set, which converts a mysterious failure into a definite answer about where the mismatch is.
Also known as: jumbo frame, jumbos, 9000 MTU