mediaproxy spends much of the CPU to handle the call compared with rtpproxy. From the result that I made in the load test, the number of concurrent call is much much less than we expected. maximum concurrent call using mediaproxy (openser & mediaproxy in the same server): 30 maximum concurrent call using rtpproxy (openser & rtpproxy in the same server): 60 Call making over the above limitatioin will cause the system unstable and busy with message 481 and 408. I have already using the basic configuration file downloaded from http://www.onsip.org/modules/mydownloads/singlefile.php?cid=7&lid=24
From the above result, I wonder the performance of openser that it can
handle the calls. I may test it in the wrong way but it is what I have done in the simple way. Anyone can tell me how you can do the load test of openser with sipp?
On 5/26/06, Script Head <[EMAIL PROTECTED]> wrote:
I think the problem in this test is the mediaproxy. It's extremely slow, in my experience it's much slower than rtpproxy. That is no way a problem with SER. On 5/26/06, unplug <[EMAIL PROTECTED]> wrote: > Hi , > I have done some tests in the environment below. > PC1: sipp > PC2: openser+mediaproxy (NAT) > script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz > > Below is the testing parameter shown in sipp > 3 calls / second > concurrent call: 30 > Over 30 concurrent calls, message 481 begins to happen. The CPU usage > of PC2 is almost 90% and then PC2 will hang. > > As I expect openser should handle over thousand of calls but there is > a different between my testing. What I miss to configure for getting > more concurrent call? > > On 5/26/06, Daniel-Constantin Mierla <[EMAIL PROTECTED]> wrote: > > > > On 05/26/06 04:33, unplug wrote: > > > Hi, > > > How about using openser to handle over several hundred calls per > > > second? > > > > Very important is your configuration script. If you run openser just as > > a simple proxy, then it can go up to thousands of call setups per > > second. The performances increase if you use it in stateless mode - > > suitable for load balancing/dispatching. > > > > The only way to measure the real capacity of your platform is to set it > > up in a lab and then perform some tests using tools like sipp. > > > > Daniel > > > > > If not possbile, what is the limitation of openser to handle > > > call? > > > > > > On 5/26/06, Daniel-Constantin Mierla < [EMAIL PROTECTED]> wrote: > > >> Hello, > > >> > > >> On 05/25/06 07:26, Script Head wrote: > > >> > Hello, > > >> > > > >> > I am deploying OpenSER to distribute calls for a number of Asterisk > > >> > boxes. I believe there are some people on this list to have a similar > > >> > setup. I'd like to know what kind of hardware do you guys run OpenSER > > >> > on and how many calls per second can you set up with your specs. I am > > >> > looking to set up about 30-40 calls per second so I was wondering what > > >> > kind of hardware I'd need. > > >> a usual pc nowadays should do it without any problems. The amount of > > >> registered users influence the memory usage, the 30-40 call setups per > > >> second has no big impact in the system. > > >> > > >> Cheers, > > >> Daniel > > >> > > >> > > > >> > ScriptHead > > >> > > > >> ------------------------------------------------------------------------ > > >> > > > >> > _______________________________________________ > > >> > Users mailing list > > >> > [email protected] > > >> > http://openser.org/cgi-bin/mailman/listinfo/users > > >> > > > >> > > >> _______________________________________________ > > >> Users mailing list > > >> [email protected] > > >> http://openser.org/cgi-bin/mailman/listinfo/users > > >> > > > > > > _______________________________________________ Users mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/users
