STAC Report: Redline InRush 1.0.2, using STAC-M1.OPRA v0.95

Mean latency of 27 micros at 2x playback rate with 5 partially overlapping clients. System withstood the max rate possible with this harness: 2.8million msgs/sec (post line-arb).

STAC has released benchmark results for the InRush(TM) embedded ticker plant from Redline Trading Solutions. In addition to the InRush software, the stack under test consisted of five HP DL380 servers that consumed directly from the network that was delivering the OPRA UDP multicast stream from the playback mechanism (STAC Hi-Fi). Each server hosted a feed handler that ran on a board containing a Cell Broadband Engine processor, along with a test client that ran on the server’s native Intel processor via Linux. The Cell board contained its own memory and network interfaces.

This is the first public report from a project that used specifications from the STAC Benchmark Council. The tests followed version 0.95 of the STAC-M1.OPRA Benchmark specifications. These specifications have been refined over the past year and are now being considered for ratification by the trading firms on the STAC Benchmark Council.

Using a combination of wire capture and in-process instrumentation, STAC Tools measured the latency from the moment an exchange message was available to the system, to the moment the system’s API delivered the message to the test applications. Measurement uncertainty was +/- 1.5 microseconds.

The STAC-M1.OPRA specifications yield 51 unique benchmark results for a given system. Here are a few of the Redline results:

- In a scenario involving exchange playback at 2X the recorded rate and five test applications with partially overlapping watchlists (benchmark: stac-m1.OPRA.v0.95.s6.5b.LAT1), the InRush system achieved an average latency of 27 microseconds and 99th percentile latency of 42 microseconds.

- In all throughput benchmarks, Redline achieved the maximum possible throughput with this specification (15X playback, which corresponds to a one-second peak of approximately 2.8 million messages per second after line arbitration, or 5.6 million before line arb).

Click here to find both a STAC Report Summary and the full STAC Report containing a detailed analysis.

Normally, when STAC publishes results from projects based on specifications developed by the STAC Benchmark Council, only Council members will receive the detailed STAC Reports. However, for these first-ever STAC-M1 benchmark results, we are making the full STAC Report available to all STAC subscribers.