If there is a place jumbo would work. It should be on a direct connect link between identical nics. But across platforms may negate this somewhat. However, you have more than one issue. You have a client side "lag" issue. If you are maxing out one core that proc is doing a TON of processing to push packets. IIRC that was one reason for jumbo frames at all. i.e push fewer, larger packets and increase overall throughput. So maybe the driver for that gear bottlenecks. 98% utilization with larger frames would tend to suggest this and is a useful result.
So test systematically. What does iperf say? Does it show ~9Gbs? Doe Does it show higher throughput FN to Linux, or FN to 2008 or FN to Win7. How do the protocols compare.?NFS vs CIFS vs ISCSI vs FTP. Are you getting the same results when you hit the ARC? Is it always one big CPU crushing bottleneck on the client (sans jumbo)?
Bottom line is you likely tag some sort of single threaded issues around 3-400MBs from everything I've seen. Even across killer big servers we often see multiple connections or operations being necessary to max out the network.
It just sounds like there is some gear you need to get to know. Search 'Intel x520 poor performance' there is lots of information on how interrupts on this card perform, use of extra buffers, and jumbo packets. Plug and play at full utilization is a pipe dream.
Obviously I defer to cyber and jgreco. But I do think a discussion of issues met on a fresh install is relevant. Even if only pointed to after resolution. This is a good fit for something similar to an M1015 walkthrough, it becomes more useful as the gear continues to drop in price.
So test systematically. What does iperf say? Does it show ~9Gbs? Doe Does it show higher throughput FN to Linux, or FN to 2008 or FN to Win7. How do the protocols compare.?NFS vs CIFS vs ISCSI vs FTP. Are you getting the same results when you hit the ARC? Is it always one big CPU crushing bottleneck on the client (sans jumbo)?
Bottom line is you likely tag some sort of single threaded issues around 3-400MBs from everything I've seen. Even across killer big servers we often see multiple connections or operations being necessary to max out the network.
It just sounds like there is some gear you need to get to know. Search 'Intel x520 poor performance' there is lots of information on how interrupts on this card perform, use of extra buffers, and jumbo packets. Plug and play at full utilization is a pipe dream.
Obviously I defer to cyber and jgreco. But I do think a discussion of issues met on a fresh install is relevant. Even if only pointed to after resolution. This is a good fit for something similar to an M1015 walkthrough, it becomes more useful as the gear continues to drop in price.
Last edited: