Editing Small GigE Switches
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Summary Data == | ==Summary Data == | ||
− | The following data use the 8505T, | + | The following data use the 8505T, 8505T swtiches and a X-over cable: |
− | |||
− | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-latency.mx.png|center|thumb| | + | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-latency.mx.png|center|thumb|400px|Signature Graph]] |
− | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-signature.mx.png|center|thumb| | + | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-signature.mx.png|center|thumb|400px|Latency Graph]] |
− | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-throughput_vs_blocksize.mx.png|center|thumb| | + | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-throughput_vs_blocksize.mx.png|center|thumb|400px|Throughput Graph]] |
==Interesting Comparisons Frame Size == | ==Interesting Comparisons Frame Size == | ||
− | + | (8505T, 8505T, X-over) | |
+ | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-throughput_vs_blocksize-lam-mpich-mx.png|center|thumb|400px|LAM/1500, LAM/9000, MPICH-MX/9000]] | ||
+ | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-throughput_vs_blocksize-lam-MTU-size.png|center|thumb|400px|LAM run over range of MTU size]] | ||
+ | [[Image:Small_GigE_Switches_netpipe.Intel-PT-PCIe-throughput_vs_blocksize-mx-switches.png|center|thumb|400px|Switch Effect on MPICH-MX] | ||
− | + | * <a href="netpipe.Intel-PT-PCIe-throughput_vs_blocksize-lam-mpich-mx.png">LAM/1500, LAM/9000, MPICH-MX/9000</a> | |
+ | * <a href="netpipe.Intel-PT-PCIe-throughput_vs_blocksize-lam-MTU-size.png">LAM run over range of MTU size (1500-9000)</a> | ||
+ | * <a href="netpipe.Intel-PT-PCIe-throughput_vs_blocksize-mx-switches.png"></a> | ||
− | |||
− | |||
− | + | SMC GS16 Switch LAM MTU (note Jumbo frames still reduces throughput, except 3000!) | |
− | + | *<a href="netpipe.Intel-PT-PCIe-throughput_vs_blocksize-lam-MTU-size-gs16.png">LAM run over range of MTU size </a> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Mystery Is Solved== | ==Mystery Is Solved== | ||
− | Turn off Flow Control! I turned off Flow Control using Ethtool and the jumbo packets at the high end got much better, but the variability got much worse (see results below). Also, the kernel is now 2.6.26.2 (Using Fedora 8 now) More tests are needed | + | Turn off Flow Control! I turned off Flow Control using Ethtool and the jumbo packets at the high end got much better, but the variability got much worse (see results below). Also, the kernel is now 2.6.26.2 (Using Fedora 8 now) More tests are needed as well. |
− | |||
− | |||
− | |||
− | |||
− | = | + | * <a href="netpipe.Intel-PT-PCIe-throughput_vs_blocksize-tcp-flowctrl-off-ITR1.png">Netpipe TCP run over range of MTU size with Flow Control Off </a> |
Here is the Ethtool sequence I used to turn off Flow Control (check the man page for Ethtool for a full description of options). | Here is the Ethtool sequence I used to turn off Flow Control (check the man page for Ethtool for a full description of options). |