This book contains performance benchmarks using the Sentinel IP Short Message Gateway.

Topics

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 the Sentinel IP Short Message Gateway can be found on the Sentinel IP Short Message Gateway product page.

Benchmark Scenarios

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

MO Submission

In this scenario, the SCSCF sends a SIP message containing a short message to the IP-SM-GW, which then sends an MO-ForwardSM request to the SMSC. The Opencloud Scenario Simulator performs the role of SMSC and SCSCF. For details of the message processing, see MO Submission Flows

  1. The SCSCF sends a SIP Message containing a valid RP-Data payload to the IP-SM-GW.

  2. The IP-SM-GW responds to the SCSCF with a 202 Accepted message.

  3. The IP-SM-GW sends a TCAP OpenRequest to the SMSC.

  4. The SMSC replies with an OpenAccept.

  5. The IP-SM-GW sends an MO-ForwardSM request to the SMSC.

  6. The SMSC replies with an MO-ForwardSM response, and closes the TCAP dialog.

  7. The IP-SM-GW sends a SIP Message containing an RP-ACK to the SCSCF.

  8. The SCSCF replies with a 200 OK.

mo submission with report successful

CS Delivery

In this scenario, the SMSC delivers a MT SMS to the IP-SM-GW, which then sends the message over the CS network. The OpenCloud Scenario Simulator performs the role of SMSC, MSC, and HLR. For details of changes made to proxied messages and details of message processing, see MT Delivery Flows.

  1. The SMSC sends an OpenRequest containing a SendRoutingInfoForSM request to the IP-SM-GW.

  2. The IP-SM-GW proxies that message to the HLR.

  3. The HLR replies with a SendRoutingInfoForSM response.

  4. The IP-SM-GW proxies that response to the SMSC, and closes the dialog to the SMSC.

  5. The SMSC sends an OpenRequest containing an MT-ForwardSM request to the IP-SM-GW.

  6. The IP-SM-GW sends an empty OpenRequest to the MSC.

  7. The MSC response with an OpenAccept

  8. The IP-SM-GW sends the MT-Forward-SM request to the MSC on the established dialog

  9. The MSC closes the dialog

  10. The IP-SM-GW sends an OpenAccept to the SMSC, and closes the dialog.

mt cs delivery mapv2 successful

Hardware and Software

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

Hardware

benchmarks hardware

Software

Vendor Software Version

OpenCloud

Sentinel IP Short Message Gateway

2.6.0.3

OpenCloud

Rhino

2.5.0.2

OpenCloud

Scenario Simulator

2.3.0.10

OpenCloud

IN Scenario Pack

1.5.0.4

OpenCloud

SIP Scenario Pack

1.0.3.9-M1

Apache

Apache Cassandra

2.0.17

Oracle

Java

1.7.0_71

Configuration

Parameter Value

heap_size

6144M

new_size

1536M

gc_type

cms

gc_max_pause

50

gc_pause_interval

250

CMSOccupancyFraction

60

SurvivorRatio

16

MaxTenuringThreshold

2

Benchmark Results

This page contains the results for the Sentinel IP-SM-GW benchmarks, with both summaries and detailed metrics.

Context for these results are provided by the benchmark scenarios description.

Benchmarks

1000 messages per second, evenly split across the MO-Submission and CS-Delivery call flows.

1300% across 12 cores

Note Maximum theoretical CPU usage is 2400%.

2300MB average heap

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

MO-Submission

7.4ms

9.7ms

16.7ms

71.1ms

CS-Delivery

7.0ms

9.4ms

15.5ms

72.3ms

Detailed metrics

Call Rate

MO-Submission
scscf sim rate
CS-Delivery
smscB sim rate

Rhino CPU usage

rhino cluster 101 cpu

Rhino Heap usage

rhino cluster 101 heap

Rhino Activities

rhino cluster 101 stats activities

Scenario latencies

MO-Submission
scscf sim mo submission with report successful latency
CS-Delivery
smscB sim mt cs delivery mapv2 successful latency