This page summarises the results for benchmarks executed with the CAP Call Monitoring scenario. Detailed metrics follow the summary tables.

The benchmarks are run in two configurations:

  1. OCSS7 as the Initiator

  2. OCSS7 as the Responder

The CAP call monitoring scenario description has more information on how these configurations are defined.

Note Identical call rates was used for both Initiator and Responder benchmarks

Benchmarks

6000 calls per second (24000 messages per second)
Configuration Across 12 cores

OCSS7 as Initiator

209.9%

OCSS7 as Responder

252.3%
Note Maximum theoretical CPU usage is 1200%.
Configuration Average heap

OCSS7 as Initiator

750MB

OCSS7 as Responder

1200MB
Configuration 50th 90th 95th 99th

OCSS7 as Initiator

1.6ms

6.5ms

11.0ms

31.16ms

OCSS7 as Responder

1.5ms

6.1ms

10.5ms

30.6ms

Detailed metrics

Call Rate

2.1 CAP SSF sim rate
OCCS7 as the Initiator
2.2 CAP SSF sim rate
OCCS7 as the Responder

CPU usage

2.1 CAP SSF sgc cpu
OCCS7 as the Initiator
2.2 CAP SSF sgc cpu
OCCS7 as the Responder

Heap usage

2.1 CAP SSF sgc heap
OCCS7 as the Initiator
2.2 CAP SSF sgc heap
OCCS7 as the Responder

Scenario latencies

2.1 CAP SSF sim CAP initiator latency
OCCS7 as the Initiator
2.2 CAP SSF sim CAP initiator latency
OCCS7 as the Responder
Previous page Next page