Access Keys:
Skip to content (Access Key - 0)


1 IN benchmark environment and configuration (2.4.0)

Print this page

Hardware, software, and Rhino configuration

Below are the hardware, software, and Rhino configuration used for the Rhino benchmarks.

Hardware

The IN benchmark tests used the following hardware for one and two nodes.

Single node (5,000 calls per second)

Two nodes (10,000 calls per second)

Software

The IN benchmark tests used the following software.

Software Version
Java JDK 1.7.0_71
Rhino Rhino 2.4.0.4
CGIN 1.5.0.8
CGIN VPN 1.5.0.8
CGIN Signalware Back End Ulticom Signalware SP6.V
9.02SP6ECN9S6V-CentOS5-i386-64bit-1.5.0.8

Rhino configuration

For the IN benchmark tests, we made the following changes to the Rhino 2.4 default configuration.

Parameter Value Note
TCAP stack Signalware 9.0SP6V
JVM Architecture 64bit Enables larger heaps
Heap size 8192M
New Gen size 256M Increased from default of 128M to achieve higher throughput without increasing latency
Staging queue size 5000 Increased from default of 3000 to allow burst traffic
Staging threads 60 Increased from default of 30 for reduced latency at high throughput
CGIN RA tcap-fibers.max-pool-size 10 Increased from default of 4 for reduced latency at high throughput
CGIN RA tcap-fibers.queue-size 5000 Increased from default of 250 to allow load spikes without processing falling back to incoming thread
CGIN RA signalware.fiber-map-size 5000 Increased from default of 256 as required to match tcap-fibers.queue-size
Local Memory DB size 200M Increased from default of 100M to allow more in-flight calls
You can also review the Rhino configuration files we used during the test runs.


Results

Please review the IN benchmark results.

Adaptavist Theme Builder Powered by Atlassian Confluence