This book contains performance benchmarks using OpenCloud’s OCSS7.

It contains these sections:

  • Benchmark Scenarios — descriptions of each of the benchmark scenarios, and notes on the benchmark methodology used

  • Hardware and Software — details of the hardware, software, and configuration used for the benchmarks

  • Benchmark Results — summaries of the benchmarks and links to detailed metrics.

Other documentation for OCSS7 can be found on the OCSS7 product page.

Benchmark Scenarios

This page describes the scenarios and methodology used when running the benchmarks.

Benchmarks are run using two scenarios. Each scenario is run with the OCSS7 acting as the initiator and as the responder.

CAP call monitoring scenario

These scenarios consist of dialogs following the message flow:

  • The initiator sends a TC-BEGIN initiating a CAP v2 dialog, containing an CAP InitialDP operation invoke

  • The responder sends a TC-CONTINUE containing two operation invokes: CAP RequestReportBCSM(oAnswer,oDisconnect), and CAP Continue

  • The initiator delays for 10 seconds

  • The initiator sends a TC-CONTINUE containing a CAP EventReportBCSM(oAnswer) operation invoke

  • The initiator delays for 60 seconds

  • The initiator sends a TC-CONTINUE containing a CAP EventReportBCSM(oDisconnect) operation invoke

  • The dialog is ended with prearranged end on both the initiator and responder

TestCAPCallMonitoring

OCSS7 as the Initiator

In this configuration, the test system generates load, and is the initiator of the dialog. The responder is the external support system.

Response time is measured on the test system by the scenario simulator infrastructure, from immediately before submission of the TC-BEGIN to the TCAP stack, to immediately after receipt of the TC-CONTINUE containing the CAP Continue invoke from the TCAP stack.

OCSS7 as the Responder

In this configuration, the support system generates load, and is the initiator of the dialog. The test system responds to the dialog.

Response time is measured on the support system by the scenario simulator infrastructure, from immediately before submission of the TC-BEGIN to the TCAP stack, to immediately after receipt of the TC-CONTINUE containing the CAP Continue invoke from the TCAP stack.

MAP SRI for SM scenario

These scenarios consist of dialogs following the message flow:

  • The initiator sends a TC-BEGIN initiating a MAP dialog, containing SEND-ROUTING- INFO-FOR-SM invoke

  • The responder immediately responds with a TC-END containing a SEND-ROUTING- INFO-FOR-SM result

TestSRIforSM

OCSS7 as the Initiator

In this configuration, the test system generates load, and is the initiator of the dialog. The responder is the external support system.

Response time is measured on the test system by the scenario simulator infrastructure, from immediately before submission of the TC-BEGIN to the TCAP stack, to immediately after receipt of the TC-END from the TCAP stack.

OCSS7 as the Responder

In this configuration, the support system generates load, and is the initiator of the dialog. The test system responds to the dialog, sending a TC-END.

Response time is measured on the support system by the scenario simulator infrastructure, from immediately before submission of the TC-BEGIN to the TCAP stack, to immediately after receipt of the TC-END from the TCAP stack.

Test setup

Each test run consists of a 10 minute ramp-up period where load is increased from zero to the target rate; then a 30 minute measurement period at peak load; then a 2 minute drain period during which no new dialogs are initiated.

The ramp-up period is included as the Oracle JVM provides a Just In Time (JIT) compiler. The JIT compiler compiles Java bytecode to machinecode, and recompiles code on the fly to take advantage of optimizations not otherwise possible. This dynamic compilation and optimization process takes some time to complete. During the early stages of JIT compilation/optimization, the node cannot process full load. JVM garbage collection does not reach full efficiency until several major garbage collection cycles have completed.

Only latency measurements during the measurement period are used; latency measurements during the ramp-up period are ignored.

Load is not stopped between ramp up and starting the test timer.

Hardware and Software

This page describes the hardware and software used when running the benchmarks.

Hardware

OCSS7 benchmarks hardware
Server Name Specification OS

pm-cluster-rhel6-1a

HP DL380 G7 2X Intel Xeon X5660 2.8 GHz 12 Core, 36GB memory

RHEL 6.8

pm-cluster-rhel6-1b

HP DL380 G7 2X Intel Xeon X5660 2.8 GHz 12 Core, 36GB memory

RHEL 6.8

Software

Vendor Software Version

Oracle

Java

JDK 1.8.0_60 (64 bit)

OpenCloud

OpenCloud OCSS7

2.0.0.0

OpenCloud

Scenario Simulator

2.3.0.8

OpenCloud

IN Scenario Pack

1.5.4.0

Configuration

SGC Configuration
Parameter Value

Heap size

2048M

GC Type

CMS

com.cts.ss7.commsp.server.sendQueueCapacity

1024

sgc.ind.pool_size

20000

sgc.req.pool_size

20000

sgc.worker.threads

32

Server Kernel Parameters
Parameter Value

net.sctp.rto_min

80

net.sctp.sack_timeout

70

net.core.rmem_max

2000000

net.core.wmem_max

2000000

Benchmark Results

A summary of the benchmark results follows. Click on a benchmark name for detailed results.

Benchmark Rate CPU Usage

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%

20000 calls per second (40000 messages per second)

Configuration Across 12 cores

OCSS7 101 as Initiator

270.0%

OCSS7 101 as Responder

260.0%

OCSS7 102 as Initiator

210.0%

OCSS7 102 as Responder

210.0%

CAP Call Monitoring scenario

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

MAP SRI for SM scenario

This page summarises the results for benchmarks executed with the MAP SRI for SM 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 MAP SRI for SM scenario description has more information on how these configurations are defined.

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

Benchmarks

20000 calls per second (40000 messages per second)

Configuration Across 12 cores

OCSS7 101 as Initiator

270.0%

OCSS7 101 as Responder

260.0%

OCSS7 102 as Initiator

210.0%

OCSS7 102 as Responder

210.0%

Maximum theoretical CPU usage is 1200%

Configuration Average heap

OCSS7 101 as Initiator

1100MB

OCSS7 101 as Responder

1100MB

OCSS7 102 as Initiator

1100MB

OCSS7 102 as Responder

1100MB

Configuration 50th 90th 95th 99th

OCSS7

1.1ms

1.6ms

3.2ms

12.5ms

Detailed metrics

Call Rate

SMSC sim rate
OCCS7 as the Initiator
HLR sim rate
OCCS7 as the Responder

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

SMSC sim TestSRIforSM latency
OCCS7