Below are the hardware, software, and Rhino configuration used for the CGIN benchmarks.
Software
The CGIN benchmark tests used the following software.
| Software | Version |
|---|---|
Java |
JDK 1.6.0_18 |
Rhino |
Rhino 2.3.0.0 |
CGIN |
1.5.0.8 |
CGIN VPN |
1.5.0.8 |
CGIN Signalware Back End |
Ulticom Signalware SP6.V |
Rhino configuration
For the CGIN benchmark tests, we made the following changes to the Rhino 2.3 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 up to 1s worth of burst traffic |
Staging threads |
60 |
Increased from default of 30 for reduced latency at high throughput |
CGIN RA |
10 |
Increased from default of 4 for reduced latency at high throughput |
CGIN RA |
5000 |
Increased from default of 250 to allow load spikes without processing falling back to incoming thread |
CGIN RA |
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. |
