Hardware
Client host (epam1)
- Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz (2 CPU Hyper-Trading Enabled, 20 Cores)
- RAM 128 GB, 2133 MHz
- NIC Solarflare Communications SFC9120 (Firmware-version: 4.2.2.1003 rx1 tx1)
- Linux (CentOS 7.0.1406 kernel 3.10.0-123.el7.x86_64)
- SolarFlare driver version: 4.1.0.6734a
Server host (epam2)
- Intel(R) Xeon(R) CPU E5-2643 v3 @ 3.40GHz (2 CPU Hyper-Trading Enabled, 24 Cores)
- RAM 128 GB, 2133 MHz
- NIC Solarflare Communications SFC9120 (Firmware-version: 4.2.2.1003 rx1 tx1)
- Linux (CentOS 7.0.1406 kernel 3.10.0-123.el7.x86_64)
- SolarFlare driver version: 4.1.0.6734a
Description
Single Session Echo Scenario
- FIXAJ has one acceptor session configured on server host.
- Client application has one initiator session configured on client host.
The overall process is following:
- Client application connects to the FIXAJ instance and sends 200000 FIX 4.2 messages with a rate of 5000 messages per second.
- FIXAJ receives the messages and matches it to the same session using business layer logic.
- FIXAJ responds to the client application with the same message in the same session.
The response time measured by client application is the difference between timestamps:
- t1 - timestamp taken right before sending message to client session;
- t2 - timestamp taken right after received the same message in client back from FIXAJ.
The round-trip time formula is: RTT=t2-t1 and measured in microseconds.
Results
Single session, usec | |
---|---|
Max | 196.095 |
99.99% | 166.911 |
99.9% | 57.343 |
99% | 13.727 |
95% | 12.959 |
90% | 10.671 |
Average | 10.24 |
75% | 10.039 |
Median | 9.735 |
50% | 9.735 |
Min | 9.264 |