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 101 as Initiator

150.0%

OCSS7 101 as Responder

140.0%

OCSS7 102 as Initiator

140.0%

OCSS7 102 as Responder

140.0%

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

OCSS7 101 as Initiator

1200MB

OCSS7 101 as Responder

1200MB

OCSS7 102 as Initiator

1200MB

OCSS7 102 as Responder

1200MB

Configuration 50th 90th 95th 99th

OCSS7

1.0ms

1.3ms

2.2ms

15.7ms

Detailed metrics

Call Rate

SSF sim rate
OCCS7

CPU usage

PC101 0 cpu
OCCS7 101 as the Initiator
PC101 1 cpu
OCCS7 101 as the Responder
PC102 0 cpu
OCCS7 102 as the Initiator
PC102 1 cpu
OCCS7 102 as the Responder

Heap usage

PC101 0 heap
OCCS7 101 as the Initiator
PC101 1 heap
OCCS7 101 as the Responder
PC102 0 heap
OCCS7 102 as the Initiator
PC102 1 heap
OCCS7 102 as the Responder

Scenario latencies

SSF sim TestCAPCallMonitoring latency
OCCS7
Previous page Next page