Hardware, software, and Rhino configuration
Below are the hardware, software, and Rhino configuration used for the Rhino benchmarks.
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)
The IN benchmark tests used the following software.
|CGIN Signalware Back End
||Ulticom Signalware SP6.V|
For the IN benchmark tests, we made the following changes to the Rhino 2.4 default configuration.
|| Signalware 9.0SP6V
|| Enables larger heaps |
|New Gen size
|| Increased from default of 128M to achieve higher throughput without increasing latency |
|Staging queue size
|| Increased from default of 3000 to allow burst traffic |
|| Increased from default of 30 for reduced latency at high throughput |
|CGIN RA tcap-fibers.max-pool-size
|| Increased from default of 4 for reduced latency at high throughput |
|CGIN RA tcap-fibers.queue-size
|| Increased from default of 250 to allow load spikes without processing falling back to incoming thread |
|CGIN RA signalware.fiber-map-size
|| Increased from default of 256 as required to match tcap-fibers.queue-size |
|Local Memory DB size
|| Increased from default of 100M to allow more in-flight calls |
Please review the IN benchmark results.