Telestax is pleased to announce the result of our load test performed using the latest iteration of Telscale SMSC Gateway. The load test was performed on an Amazon cloud server with the follow specifications
Amazon Cloud Server specification
Model | vCPU | Mem (GiB) | SSD Storage (GB) | Dedicated EBS Throughput (Mbps) |
m4.2xlarge | 8 | 32 | EBS-only | 1,000 |
Server configuration
- Java version JDK version 7
- Telscale version Telscale-smsc-6.2.2.672
- Cassandra apache-cassandra-2.0.17-src.tar.gz
- JAVA_OPTS=”-Xms12g -Xmx12g -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000″
Test Result
The Cassandra and Telscale SMSC gateway ran on the same server.
Using the integrated SMPP load test tool, 1 Million SMS messages were sent to the Telscale SMSC server.
Processing was finished in 16 mins and 28 seconds
Processing an average of 1000 messages per second
Result after successful load test
4 [main] INFO org.mobicents.protocols.smpp.load.Client - submitToSend=1000000
4 [main] INFO org.mobicents.protocols.smpp.load.Client - startDestNumber=9960200000
4 [main] INFO org.mobicents.protocols.smpp.load.Client - destNumberDiff=10000
5 [main] INFO org.mobicents.protocols.smpp.load.Client - endDestNumber=9960210000
5 [main] INFO org.mobicents.protocols.smpp.load.Client - sourceNumber=6666
5 [main] INFO org.mobicents.protocols.smpp.load.Client - peerAddress=127.0.0.1
6 [main] INFO org.mobicents.protocols.smpp.load.Client - peerPort=2776
6 [main] INFO org.mobicents.protocols.smpp.load.Client - systemId=test
6 [main] INFO org.mobicents.protocols.smpp.load.Client - password=test
7 [main] INFO org.mobicents.protocols.smpp.load.Client - message=Hello World
85 [main] INFO org.mobicents.protocols.smpp.load.Client - Waiting up to 7 seconds for all sessions to bind...
171 [main] INFO org.mobicents.protocols.smpp.load.Client - Sending signal to start test...
987428 [pool-5-thread-1] INFO org.mobicents.protocols.smpp.load.Client - before waiting sendWindow.size: 0
987436 [pool-5-thread-1] INFO org.mobicents.protocols.smpp.load.Client - Final Session rx-submitSM[request=0 expired=0 response=0 avgWaitTime=0.0ms avgResponseTime=0.0ms avgEstimatedProcessingTime=0.0ms cmdStatus=[]]
987440 [pool-5-thread-1] INFO org.mobicents.protocols.smpp.load.Client - Final Session tx-submitSM[request=1000000 expired=0 response=1000000 avgWaitTime=0.8ms avgResponseTime=9759.8ms avgEstimatedProcessingTime=0.5ms cmdStatus=[0=1000000]]
987440 [pool-5-thread-1] INFO org.mobicents.protocols.smpp.load.Client - after waiting sendWindow.size: 0
987444 [main] INFO org.mobicents.protocols.smpp.load.Client - Performance client finished:
987445 [main] INFO org.mobicents.protocols.smpp.load.Client - Sessions: 1
987445 [main] INFO org.mobicents.protocols.smpp.load.Client - Window Size: 10000
987446 [main] INFO org.mobicents.protocols.smpp.load.Client - Sessions Failed: 0
987446 [main] INFO org.mobicents.protocols.smpp.load.Client - Time: 987273 ms
987446 [main] INFO org.mobicents.protocols.smpp.load.Client - Target Submit: 1000000
987447 [main] INFO org.mobicents.protocols.smpp.load.Client - Actual Submit: 1000000
987447 [main] INFO org.mobicents.protocols.smpp.load.Client - Throttled Message count: 0
987449 [main] INFO org.mobicents.protocols.smpp.load.Client - Throughput: 1012.891 per sec
987450 [main] INFO org.mobicents.protocols.smpp.load.Client - Session 0: submitSM [request=1000000 expired=0 response=1000000 avgWaitTime=0.8ms avgResponseTime=9759.8ms avgEstimatedProcessingTime=0.5ms cmdStatus=[0=1000000]]
987450 [main] INFO org.mobicents.protocols.smpp.load.Client - Shutting down client bootstrap and executors...
987456 [main] INFO org.mobicents.protocols.smpp.load.Client - Done. Exiting
BUILD SUCCESSFUL
Total time: 16 minutes 28 seconds
As you can see from the build result above, the whole process took a little over 16 minutes. The throughput of 1012.891 per second.CPU and Memory Usage
The CPU usage peaks at about 60 percent at the height of the load with constant traffic from the SMPP Load test.
The CPU and memory usage is shown in the screenshot below.