Hello all, I believe I am not the only one who is conducting stress testing. Could you please share you results: I am particularly interested in amount of concurrent calls that could be achieved with the smallest deployment.
BR, Stanislav Khalup From: Stanislav Khalup Sent: Friday, September 9, 2016 6:09 PM To: [email protected] Cc: Denis Plotnikov <[email protected]> Subject: Stress test results Hello team, At last after updating to the latest release, limiting all VMs to 1CPU/2GB Ram and setting all settings to default we managed to stop IMS cluster from crashes. The thing is we see the same results while performing stress tests. After some time the system closes socket regardless of ongoing calls. Is this kind of behavior normal for Clearwater IMS. I attach the full sipp logs and screens archive. Please look at graphic for network usage that shows downfall of traffic when sockets are being closed: https://www.dropbox.com/s/q2l3nsaxyu6sf32/sipp_stress.tar.gz?dl=0 Another question that is bothering me is how to interpret the results of stress testing? How can you evaluate that your deployment is hitting the limit? All the orchestration demos out there show that new nodes are added when CPU utilization reaches some 30% but in our test we could never see such loads even with 1-1 Bono and Sprout. Judging from the bucket algorithm description we assumed that refused connections metric should indicate that the system is at the limit but this snmp statistics is always zero in all our tests. So, how are you processing the results of stress test? What metrics are you looking at? BR, Stanislav Khalup
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
