The following was measured on an SU300-80F (1200 RPF, with BS2000 OSD/BC V11.0 and openNet Server V4.0):
Transaction-oriented load
Maximum transaction rate approx. 66,000 TA/s with 100% CPU utilization
Best mean response time approx. 0.5 milliseconds
Throughput-oriented load for parallel connections
With throughput-oriented mode the CPU utilization depends on the message length. The longer the message, the lower the BS2000 CPU requirement. This dependency does not exist when receiving. Both when sending and receiving, the CPU requirement increases with the number of parallel connections.
The table below shows the maximum throughput and the CPU utilization for 64 KB and 8 KB messages on an SU300-80F for a 1GbE and for a 10 GbE, each with 16 parallel connections and both with standard frames and with jumbo frames.
MTU[bytes] | 10 GbE 1500 | 10 GbE 9000 | 1 GbE 1500 | 1 GbE 9000 | ||||
Send | Receive | Send | Receive | Send | Receive | Send | Receive | |
MB/s | 1125 | 1100 | 1180 | 1080 | 112 | 112 | 118 | 118 |
CPU% for 64KB | 48 | 48 | 50 | 50 | 11 | 40 | 7 | 29 |
CPU% for 8 KB | 87 | 48 | 93 | 50 | 15 | 40 | 11 | 28 |
Both the 1 GbE and the 10 GbE can be fully utilized.
Throughput with one connection
The 1 GbE is fully utilized with one connection both when sending and when receiving: 110-120 MB/s is achieved. The CPU utilization is about 10% in this case.
The following applies for a 10 GbE with one connection:
When sending, the throughput depends on the message length. Approximately the following throughput was achieved with both standard frames and with jumbo frames:
220 MB/s with a message length of 8 KB (CPU utilization 17%)
550 MB/s with a message length of 32 KB (CPU utilization 21%)
800 MB/s with a message length of 64 KB (CPU utilization 22%)
When receiving, the throughput depends on the message length and amounts to more than 900 MB/s both with standard frames and with jumbo frames.