How To Enable Jumbo Frames
Enabling jumbo frames can significantly increase your network’s throughput while consuming fewer CPU cycles (we’ll explain why in a moment). But before you configure your PCs to use jumbo frames, you should know that their value lies primarily in speeding up large file transfers within your network (versus to and from the Internet).
You should also be aware that enabling jumbo frames might cause problems with latency sensitive network applications, such as VoIP and online games. Lastly, jumbo frames are available only on gigabit networks, and every device in the path of the file transfer—all your switches (starting with the one in the router), your PC, server, and/or NAS—must all be equipped with gigabit Ethernet interfaces. What’s more, each of those devices must be capable of passing the same size jumbo frames. Okay, here’s another twist: There is no such thing as a standard-size jumbo frame.
Confused? Here’s a brief Ethernet primer: Data travels over an Ethernet network in frames, with each frame containing a 1,460-byte payload (the data being transferred) plus a 40-byte TCP/IP header. Add these together and you have Ethernet’s 1,500-byte maximum transmission unit (MTU). Now add the 12-byte Ethernet frame header, two bytes that identify the Ethernet type, and four bytes of error-detection data and you get a standard-sized Ethernet frame of 1,518 bytes.
A jumbo frame is simply an Ethernet frame that’s larger than 1,518 bytes. Since the header sizes remain the same, each frame can carry a larger payload. You’ll see the greatest benefit from enabling jumbo frames when you transfer large files across your network. Since fewer frames are needed to carry the same amount of data, transfer speeds go up and CPU utilization goes down. (CPU utilization probably isn’t an issue on your PC, but your server or NAS almost certainly has a fraction of that horsepower.)
The tricky part is determining the optimum size frame that everything supports, and that will take a little trial-and-error benchmarking to figure out. Gigabit Ethernet supports a maximum MTU of 9,000 bytes; but if you push your network too hard, performance might deteriorate as dropped and fragmented frames are constantly resent.

Your PC's network interface probably came from the factory with jumbo frames disabled.
As we mentioned, the value of using jumbo frames manifests itself during large file transfers. So before you make any changes to your gear’s MTU settings, determine your network’s baseline performance by using a stopwatch to measure how long it takes to copy a large file—a DVD ISO image, for instance—from a client to a server or a NAS box across your network and back again.
On a PC running Windows 7, click the Start menu and then right-click on Computer and choose the Manage option. Click on Device Manager in the left-hand column, click on Network adapters in the center column, and then right-click on the network adapter you’re using to connect to your network and choose Properties. Click on the Advanced tab and look for Jumbo Frame in the Property window. Now, choose the MTU size you wish your NIC to operate with.
You’ll need to do the same thing with your server or NAS device (most NAS boxes have a Web interface for this purpose, so you should refer to its documentation for specifics). Although each device in the path of the transfer needs to be configured to use the same size jumbo frame, you probably won’t be able to manually configure the switch in your router or even a stand-alone switch if it’s an unmanaged model (the most common type in the consumer market). Fortunately, you won’t need to: You’re golden as long as the router’s and any stand-alone switch you use support jumbo frames.
Once you’ve tweaked the MTU values on each device’s network interface, measure how long it takes to copy that same file across the network. If you get a bump in speed with a 4K MTU, try 9K. If performance degrades at that size, dial it back until you find the optimum value.
![]()
JEEPMON
January 08, 2011 at 10:08pm
I am sure this is the most common and popular setup and a very important question. say you have several computers in your house all hard wired (ethernet)up through a wireless router that is connect to a moden (dsl or cable) to the internet. There is also a NAS or a home server for sharing,backups, and storage. All of the computers support jumbo frames as well as the router and the NAS. I can see ho jumbo frames would help if enables for transfers to and from the computers and the server/NAS. BUT will enabling the jumbo frames make for slower more fragmented packets when the computers are connecting to the internet and downloading stuff? The cable/DSL modem is only 10/100 no gigabit or jumbo frames. Will enabling jumbo frames hurt internet connections and downloads in this setup?
![]()
JEEPMON
January 08, 2011 at 10:08pm
I am sure this is the most common and popular setup and a very important question. say you have several computers in your house all hard wired (ethernet)up through a wireless router that is connect to a moden (dsl or cable) to the internet. There is also a NAS or a home server for sharing,backups, and storage. All of the computers support jumbo frames as well as the router and the NAS. I can see ho jumbo frames would help if enables for transfers to and from the computers and the server/NAS. BUT will enabling the jumbo frames make for slower more fragmented packets when the computers are connecting to the internet and downloading stuff? The cable/DSL modem is only 10/100 no gigabit or jumbo frames. Will enabling jumbo frames hurt internet connections and downloads in this setup?
![]()
DrGerm
August 21, 2010 at 5:40am
I see that Jumbo Frames might help with transferring large files (like an ISO or a large VOB file) but does this help with streaming these same files. I have a server that I connect to a theatre PC and use MyMovies and have a mixed library of DVD folders and Blu-Ray ISO's. Any thoughts?
![]()
theresapartyinm...
August 18, 2010 at 1:22pm
If you are just sending a steady stream of voice packets or packets from games the larger MTU will never be used. If jumbo frames are going out with voice packets yes there will be a latency gain, but it's the same latency gain that 1518byte frames cause. The data packets larger than a voice frame being transmitted quickly will cause latency due to lack of priority for the voice packets, not the size of the frames.
![]()
sotoa
August 18, 2010 at 6:07am
I've read about jumbo frames in the past and according to smallnetbuilder.com, he suggests that you use 4K. My switches are jumbo frame capable but not my routers. I figure I can at least copy from computer to computer a little faster.
One thing I've noticed, the new Dell Vostro line has gigabit lan, but no jumbo frame option at all. I wonder why.
![]()
gendoikari1
August 17, 2010 at 1:40pm
The device properties for my network adapter (Marvell Yukon 88E8056) doesn't have "Jumbo Frame", but rather "Jumbo Packet", with settings of 1514 (default), 4088 and 9014 bytes. Probably depends on adapter.
![]()
BluePhoton
August 17, 2010 at 1:09pm
What is a normal throughput for an optimized home network?
I was getting ~4MB/s throughput while copying large files from a local computer to my NAS. I then switched to Teracopy, and the throughput went up to about ~11MB/s. But is that good?
![]()
aviaggio
August 17, 2010 at 3:04pm
Not really. Sounds like fast Ethernet (100 Mb/s = 12.5 MB/s), not gigabit. With gigabit you should see speeds in the 35-55 MB/s range.
![]()
bear
August 17, 2010 at 11:37am
Another option is to use an old-school technique used for getting the most out of that fax/modem:
ping -f -l <mtu size> <ip of lan machine with most hops from the one you're pinging on>
and adjust the mtu size until the packets are no longer fragmented.
For instance:
5 gigabit hops from 192.168.0.100 to 192.168.0.263
C:\Documents and Settings\192.168.0.100>ping -f -l 9216 192.168.0.263
if the MTU is too high, you'll get a message:
"Packet needs to be fragmented but DF set."
just keep lowering it until you no longer get that message. That's likely where you'll find the "sweet spot" for your network.














