On 27/03/2017 21:15, Alex Balashov wrote:
You might be running into semi-invisible/not widely publicised (but definitely very real) PPS limits on given instance sizes.
I assume you refer to AWS instance packets per second limits -- I was not aware of it, although I expected somehow. Has anyone encountered a similar situation and can share some numbers that they faced during past experiences? It would be useful to have in mind when dimensioning sip server deployments...
Cheers, Daniel
On March 27, 2017 3:09:56 PM EDT, Jade SZ jitterbuffer@gmail.com wrote:
Hi Guys,
I am running a simple REGISTER load test on:
- Kamailio sever with 2 cores - mem 5G
- Kamailio server with 4 cores - mem 16G
Both are EC2 instances.
At -r = 500 i.e. 500 reg/sec sipP test works fine with very few re-trans. But when i increase it to 800 reg/sec it starts retransmissions in bulk.
I don't see server's CPU, load-avg or memory shooting. Running everything by default, even using kamctl to start the instance. So I have not tuned any params yet.
My main concern is how can I make server choke and get its actual capacity, and avoid these retransmissions as apparently kamailio is not even utilizing 2 cores and CPU usage is under 10 always.
Results of both server is same i.e. 500 reg/sec max so I am sure there is some problem that needs a fix, but need some hints here.
Also used multiple SIPp's to rule out if it is SIPp issue, but after 500 I see same problem.
Regards, JSZ
-- Alex
-- Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users