Call rate
The benchmark was run at the maximum sustainable load level for the Sh Cache Microservice. 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).
The benchmark is run at 700 sessions per second split unevenly across all scenarios. Scenarios are weighted unequally to mimic the GET heavy workload expected of the Sh Cache Microservice. We expect a GET heavy workload, as the TAS does multiple SH GET queries for many call flows. HSS writes (and resulting PUTs/POSTs) are comparatively rare.
Scenario |
Percentage |
35% |
|
35% |
|
10% |
|
10% |
|
10% |
Scenario latencies
| Scenario | 50th percentile | 75th percentile | 90th percentile | 95th percentile | 99th percentile |
|---|---|---|---|---|---|
get-mmtel-services |
7.3ms |
17.1ms |
66.3ms |
155.4ms |
325.8ms |
get-msisdn |
6.1ms |
17.2ms |
66.5ms |
156.5ms |
326.1ms |
put-mmtel-services |
7.5ms |
22.8ms |
73.3ms |
164.1ms |
336.6ms |
put-stn-sr |
6.5ms |
20.8ms |
70.6ms |
162.2ms |
333.2ms |
ue-reachability-subscribe |
3.0ms |
11.9ms |
59.4ms |
146.3ms |
320.9ms |
