Mike O'Connor wrote: Does this really cause a performance drop from 420 to 50 sessions? regards klaus > > I would switch your machines make your test machine your production and > then buy a second machine of the same spec and use the SRV record load > balancing to give you both higher performance and redundancy. > > All in all your better off having 3 or 4 machine than one machine in the > long term any :) > > Cheers > Mike > > > > Tung Tran wrote: >> Hi all, >> >> I've tested the performance of mediaproxy as below: >> >> 1/ PC1: Single P4, 2.4Ghz , 1GB memory, it can handle 420 sessions >> using rtpgenerator with g729. (testing server) >> 2/ PC2: Dual-xeon 3Ghz, 2GB memory, but it just can handle about 50 >> sessions when I use rtpgenerator with g729. (production server) >> >> Should anybody can help me to customize my production server to handle >> more sessions. >> >> Thanks and regards >> >> Tung. >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users

Hi all, I just install another distributor linux: Red hat Enterprise Advance server 4, and got better result. The same server can handle about 400 sessions, (my first test was runing on CentOS 5) Yes Mike is right, SMP does not help to handle more session than single CPU server.

Hi, I´ve seen rtpproxy with more then 400 concurrent session, without any problems.. so I know rtpproxy can do it :) (not sure about mediaproxy though)