Call rate

Benchmarks were run at the maximum sustainable load level for each node. In this configuration there is no tolerance for node failure, any additional incoming messages will be dropped. To allow for node failure, additional nodes need to be added to provide an acceptable margin (an N+K configuration).

2000 sessions per second split across all three scenarios. This is 666.6 sessions per second each of MO Submission, MT-PS-Delivery, and Third party registrations.

Assuming that we have the Subscriber Definition, and run with K=0 no redundancy, we can support 1.2 million standard subscribers.

Note Latency is not measured for the third party registration scenario. A delay in processing registrations is not customer visible, unless it is excessive enough to failure in our test tools.

Scenario latencies

Scenario 50th percentile 75th percentile 90th percentile 95th percentile 99th percentile

MT-PS-Delivery

31.5ms

51.1ms

86.5ms

114.6ms

239.8ms

MO-Submission

7.8ms

12.2ms

25.5ms

44.6ms

103.2ms

Detailed metrics

Rhino CPU usage

Node 101

Node 102

Node 103

Rhino heap usage

Node 101

Node 102