Test procedure

  • Calls were evenly distributed between all available cluster nodes.

  • All calls had a duration of 60s.

  • MAP queries were required for 10% of calls.

  • Benchmarks were taken over a two-hour test run, with an additional 15 minutes for JIT compilation.


Cluster size Calls / sec TCAP messages / sec Events / sec Results

One node




Two nodes




SLEE events per second dramatically exceed the TCAP message count in the table above because each inbound TCAP message generates:

  • one event for itself;

  • a dialog state change event, if appropriate (e.g. the first TC-Continue received after sending a TC-Begin indicates dialog acceptance); and

  • one event for each TCAP component the TCAP message contains (e.g. an operation or a response).

Outbound messages do not trigger events.

Types of graphs

The individual test results include the following types of graphs:

Response times

Distribution of response-time changes during the course of the test run.

Response time distribution

Overall distribution of response times from the entire test run.

CPU utilization

Percentage of CPU used by Rhino nodes, as measured by vmstat.


Heap usage.

Previous page Next page