Hello Jim, On 09/20/08 00:03, Jim dalton wrote: > We ran a benchmark test of OpenSER and RTPproxy to understand the relation > between CPU capacity and the number of simultaneous calls that could be > managed with acceptable call quality. > > OpenSER and RTPproxy were hosted on a Dell Precision 490 server with two > Intel Xeon 5140 dual core, 2.33 GHz CPUs and 4 GB of RAM. Three CPU cores > were disabled for the test. The test was run using just a single CPU core. > Multiple SIPp clients directed traffic to OpenSER which queried an OSP > server for call routing instructions. The test was designed for each call > to require an average of two retries before the call was completed to a SIPp > server on the third try. The two-way RTP stream for each call flowed > through the RTPproxy. Call Detail Records for each call attempt were sent > from OpenSER to the OSP server. > > 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 > > thanks for sharing the results! I wonder if you could get the share of cpu used by openser during testing.
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 Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com _______________________________________________ Users mailing list [email protected] http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
