Single node benchmark

Call rate

  • 5,000 calls per second

  • 12,500 dialogs per second

Throughput

5000 full rate

Response time (ms)

(call setup time)

  • 50% of calls in 12ms

  • 75% of calls in 20ms

  • 90% of calls in 35ms

  • 95% of calls in 49ms

Response time

5000 full rtt

Response time distribution

5000 full rttdist

CPU usage

  • Node 1: 39%

CPU - Node 1

5000 full volcano1 cpu

Heap

Heap - Node 1

5000 full volcano1 heap

Two node benchmark

Call rate

  • 10,000 calls per second (5,000 calls per node)

  • 25,000 dialogs per second

Throughput

10000 full rate

Response time (ms)

(call setup time)

  • 50% of calls in 19ms

  • 75% of calls in 30ms

  • 90% of calls in 47ms

  • 95% of calls in 61ms

Response time

10000 full rtt

Response time distribution

10000 full rttdist

CPU usage

  • Node 1: 39%

  • Node 2: 39%

CPU - Node 1

10000 full volcano1 cpu

CPU - Node 2

10000 full volcano2 cpu

Heap

Heap - Node 1

10000 full volcano1 heap

Heap - Node 2

10000 full volcano2 heap

Notes

  • All calls are monitored for the entire duration on the originating leg.

  • The switch simulator measures call-setup time from when it sends the InitialDP to the application until it receives the corresponding response.

  • The response time (or "call-setup" time) is the time between sending the InitialDP (1) and receiving the Connect (2), as measured by the switch.

  • The response time includes the time for any MAP query to the HLR that the application may have performed.

  • To calculate the number of dialogs (for example, using 5,000 calls per second):

    • All calls involve originating and terminating treatment (in our example, this means 10,000 dialogs)

    • 50% of calls involve a query to the HLR (2,500 dialogs).

    ... for a total of 12,500 dialogs per second.

Previous page