STAC Network I/O Testing Program - SUMMARY PAGE

The STAC Network I/O Testing Program is a series of testing projects, most of which are requested by the STAC Network I/O SIG. These projects generally lock down all the layers of the "stack under test" (SUT) except for one or two, in order to make apples-to-apples comparisons at a given layer. For example, several tests may be run on the same server and OS while varying only the host adapter or network driver. This page is updated as new test results are made available.

Below are links to tests performed using STAC-N tools. (Note: This does not include the STAC-N pilot project, "STAC Network API Study A"). When comparing reports, please note the version of benchmark specs. Different versions cannot necessarily be compared directly.

The table at the bottom of this page indexes the reports that are available from this program to date. You may also be interested in:

A CSV file containing summary latency statistics for all configurations tested at all message rates. This enables easy analysis within Excel or another tool.

The latest package of STAC-N test harness software to run your own tests.

A slide deck covering some optimization findings from testing with RHEL 6.3 and Solarflare.

A slide deck summarizing the RHEL 6.3 v 5.8 differences with the kernel driver and OpenOnload using Solarflare adapters.

A slide deck summarizing the RHEL 6.3 v 5.8 differences with the kernel driver and Mellanox adapters.

Each report in the table below corresponds to a unique SUT. Note that a SUT is defined by all aspects of its configuration. That means that any change to the configuration (hardware, software, even a config parameter) defines a new SUT. The columns capture several components of the SUT, but not all. In the event that two SUTs have identical values for all of the components listed, the SUTs are distinguished by the configuration number in the "CONFIG" column at the far right.

 

TRANSDRIVER*SERVERNICOSCONFIG
TCPKernelIBM X3650 M4SFN6122FRHEL 6.3
Config 1
TCPOpenOnloadIBM x3650 M4SFN6122FRHEL 6.3
Config 1
UDPKernelIBM x3650 M4SFN6122FRHEL 6.3
Config 1
UDPOpenOnloadIBM x3650 M4SFN6122FRHEL 6.3
Config 1
UDPKernelIBM x3650 M4SFN6122FRHEL 5.8
Config 1
TCPKernelIBM x3650 M4SFN6122FRHEL 5.8
Config 1
TCPOpenOnloadIBM x3650 M4SFN6122FRHEL 5.8
Config 1
UDPOpenOnloadIBM x3650 M4SFN6122FRHEL 5.8
Config 1
UDPKernelIBM x3650 M4MCX354ARHEL 5.8
Config 1
TCPKernelIBM x3650 M4MCX354ARHEL 5.8
Config 1
TCPKernelIBM x3650 M4MCX354ARHEL 6.3
Config 1
UDPKernelIBM x3650 M4MCX354ARHEL 6.3
Config 1
UDPKernelIBM x3650 M4MCX354ARHEL 6.3
Config 2
UDPChelsio WireDirect UDPSM X9DR3-F/IT420-LL-CRRHEL 5.5
Config 1
RDMA/WRedHat HPNSM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
RDMA/S-RRedHat HPNSM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
TCPVMASM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
UDPVMASM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
RDMA/WMellanox OFEDSM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
RDMA/S-RMellanox OFEDSM 6027AX-TRF-HFT1MCX354ARHEL 6.3
Config 1
RDMA/S-RMellanox OFEDSM 6027AX-TRF-HFT1MCX354AUbuntu 12.10
Config 1
RDMA/WMellanox OFEDSM 6027AX-TRF-HFT1MCX354AUbuntu 12.10
Config 1
UDPChelsio WireDirect UDPSM X9DR3-FT520-LL-CRRHEL 6.4
Config 1
TCPChelsio WireDirect TOESM X9DR3-FT520-LL-CRRHEL 6.4
Config 1
UDPChelsio WireDirect UDPSM 6027AX-TRF-HFT3T520-LL-CRRed Hat Enterprise MRG Realtime
Config 1
TCPChelsio WireDirect TCPSM 6027AX-TRF-HFT3T520-LL-CRRed Hat Enterprise MRG Realtime
Config 1
UDPExablaze Exasock UDPWhite-boxExaNIC X4CentOS 6.5Config 1
TCPKernelSM 6027AX-TRF-HFT3MCX314ARHEL 6.4Config 1
TCPVMASM 6027AX-TRF-HFT3MCX314ARHEL 6.4Config 1
UDPKernelSM 6027AX-TRF-HFT3MCX314ARHEL 6.4Config 1
UDPVMASM 6027AX-TRF-HFT3MCX314ARHEL 6.4Config 1
TCPKernelSM 6027AX-TRF-HFT3SFN7122FRHEL 6.4Config 1
TCPOpenOnloadSM 6027AX-TRF-HFT3SFN7122FRHEL 6.4Config 1
UDPKernelSM 6027AX-TRF-HFT3SFN7122FRHEL 6.4Config 1
UDPOpenOnloadSM 6027AX-TRF-HFT3SFN7122FRHEL 6.4Config 1
TCPOpenOnloadSM 6027AX-TRF-HFT3SFN7122FRHEL 6.4Config 1

* SM = Supermicro

Please log in to see file attachments. If you are not registered, you may register for no charge.

The speed with which applications in the trading process (algorithmic "black boxes", matching engines, smart order routers, etc.) can get information from and to the network is a critical--sometimes decisive--contributor to their overall latency.