MSS 0.9 soak test results
24 views
Skip to first unread message
Luis Barreiro
Apr 28, 2009, 5:37:12 PM4/28/09
to mobicent...@googlegroups.com
Hi all,
Attached is the report of the latest soak test on MSS 0.9.
The tests consisted in 100 Million calls where MSS acted as UAS. Call rate was 370 caps, using TCP as transport protocol.
Total test duration was over 75 hours. In the end of the test there were 3 open calls.
CPU usage was below 45% and memory was stable at 52 %
From the report you can see that response time was 15ms average, and never above 100ms. This is an excellent result.
Regards, Luis Barreiro
The test was conduccted under the following condictions:
Host: perf08.qa.atl.jboss.com
Processor: 2 x (Dual-Core AMD Opteron(tm) Processor 2220 SE, 2800.436 MHz, cache size: 1024 KB)
[lbarreir@perf08 ~]$ cat /proc/meminfo
MemTotal: 8234060 kB
[lbarreir@perf08 ~]$ uname -r
2.6.9-42.0.10.ELsmp
[lbarreir@perf08 ~]$ $JAVA_HOME/bin/java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
JAVA_OPTS=" -Xms4096m -Xmx4096m -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseTLAB -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
MSS 0.9 with SimpleSipServlet example from SVN and all logs disabled. Concurrency control set to 'NONE' (default). Congestion control interval set to -1.
64 jain-sip threads and TCP signaling protocol
Load generator: SIPp 3.0, using the scenario file attached, started with the command:
./sipp 127.0.0.1:5080 -s yousendbye -sf uac.xml -i 127.0.0.1 -p 5050 -r 370 -m 100000000 -nd -t t5 -bg -fd 1 -trace_stat
Attached is the report of the latest soak test on MSS 0.9.
The tests consisted in 100 Million calls where MSS acted as UAS. Call rate was 370 caps, using TCP as transport protocol.
Total test duration was over 75 hours. In the end of the test there were 3 open calls.
CPU usage was below 45% and memory was stable at 52 %
From the report you can see that response time was 15ms average, and never above 100ms. This is an excellent result.
Regards, Luis Barreiro
The test was conduccted under the following condictions:
Host: perf08.qa.atl.jboss.com
Processor: 2 x (Dual-Core AMD Opteron(tm) Processor 2220 SE, 2800.436 MHz, cache size: 1024 KB)
[lbarreir@perf08 ~]$ cat /proc/meminfo
MemTotal: 8234060 kB
[lbarreir@perf08 ~]$ uname -r
2.6.9-42.0.10.ELsmp
[lbarreir@perf08 ~]$ $JAVA_HOME/bin/java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
JAVA_OPTS=" -Xms4096m -Xmx4096m -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseTLAB -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
MSS 0.9 with SimpleSipServlet example from SVN and all logs disabled. Concurrency control set to 'NONE' (default). Congestion control interval set to -1.
64 jain-sip threads and TCP signaling protocol
Load generator: SIPp 3.0, using the scenario file attached, started with the command:
./sipp 127.0.0.1:5080 -s yousendbye -sf uac.xml -i 127.0.0.1 -p 5050 -r 370 -m 100000000 -nd -t t5 -bg -fd 1 -trace_stat
Jean Deruelle
Apr 29, 2009, 3:56:46 AM4/29/09
to mobicent...@googlegroups.com
Eduardo Martins
Apr 29, 2009, 5:35:44 AM4/29/09
to mobicent...@googlegroups.com
Great results, keep up the good work.
-- Eduardo
Reply all
Reply to author
Forward
0 new messages