OpenSER and RTPproxy, using a single core of the 2.33 GHz CPU, can manage up to 750 simultaneous calls.
A summary and detailed description of the benchmark test are available at
http://www.transnexus.com/White%20Papers/OpenSER_RTPproxy_test.htm
Daniel-Constantin Mierla wrote:
thanks for sharing the results! I wonder if you could get the share of cpu used by openser during testing.
We did not record the CPU utilization for OpenSER and RTPproxy separately. Our experience shows that OpenSER CPU utilization is trivial compared to the CPU cycles required to proxy media. If we had measured OpenSER CPU utilization, we expect it would have been a very small number (<5%).
As you have access to 4 CPU cores, would be very interesting to see the impact of running 4 rtpproxy instances on the same machine and configure kamailio/openser to use all of them, to see how it really scales. nathelper module in kamailio/openser can use many rtpproxy instances at same time, doing load balancing of the rtp streams among available rtpproxies. The rtpproxy_sock parameter of nathelper module can take many rtpproxy control socket addresses: http://www.kamailio.org/docs/modules/1.3.x/nathelper.html#AEN160
Testing multiple RTPproxy instances would be a good test. We would like to do that if we return to this project.