That's a rather dated study. But it's better than a nonexistent reference point, true.
-- Alex
-- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/Mino Haluz mino.haluz@gmail.com wrote:According to this (http://transnexus.com/index.php/performance-test-results-for-openser-and-rtp...)
"For a server hosting both OpenSER and RTPproxy, each 1 GHz of CPU processing capacity can manage a maximum of 325 simultaneous calls."
I have 2.4GHz for rtpproxy, but CPU/Mem/network is ok, so the bottleneck should be somewhere else probably..
On Thu, Sep 13, 2012 at 5:56 PM, Alex Balashov abalashov@evaristesys.com wrote:
I'm not sure what a single instance of rtpproxy can handle, but most people squeezing thousand of concurrent calls per box are probably doing it on multicore boxes by binding multiple instances of rtpproxy with different core affinities, and round-robining among them.
-- Alex
-- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/
Mino Haluz mino.haluz@gmail.com wrote: The results:
- rtpproxy calls count 280
- sipp calls count 2000
- iptraf on proxy 4.8MB/s
- G711a codec
So if my calculations are right (16kB/s per stream * 280 = 4.5MB/s), rtpproxy calls count is really the right value. CPU usage is ok on every machine (rtpproxy 20-30% CPU). Does anybody know why rtpproxy cannot serve more than 270-280 calls ?
On Thu, Sep 13, 2012 at 5:07 PM, Mino Haluz mino.haluz@gmail.com wrote:
Ok, so I put there unforce_rtp_proxy even though I'm using rtpproxy_manage. The tip with nc now really shows the calls count.
But the dialog count is still higher and higher, so I have bug somewhere in the configuration. I'll check it.
On Thu, Sep 13, 2012 at 4:53 PM, Alex Balashov abalashov@evaristesys.com wrote:
Correct, but you still need to call rtpproxy_manage() on receipt of a BYE or CANCEL. It'll just figure out what to do on its own.
None of this has to do with dialog state, though. Just rtpproxy control.
-- Alex
-- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/
Mino Haluz mino.haluz@gmail.com wrote: I'm using rtpproxy_manage, so I assume unforce_rtp is not needed.
On Thu, Sep 13, 2012 at 4:10 PM, Peter Lemenkov lemenkov@gmail.com wrote:
2012/9/13 Mino Haluz mino.haluz@gmail.com:
Peter: Thanks for the tip! Really interesting. But I do not understand, why also this list contains the calls that were ended by sipp... Should I search for some mistake in my kamaillio config ?
Perhaps you don't close them with unforce_rtp_proxy:
if(method=="BYE" || method=="CANCEL"){ unforce_rtp_proxy(); }
-- With best regards, Peter Lemenkov.
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
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
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
_______________________________________________ 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
-
Alex Balashov