Rod, Registering every 60 seconds is a bad idea, and this should not be justified. You should register every 1800 seconds and send a NAT keepalive every X seconds. X should be slightly lower than the NAT UDP timeout of the router in front of the phones, if the phones are behind NAT. If the phones are not behind NAT, NAT keepalive is not necessary. David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 03/05/2010 à 15:39, Rod. a écrit :
Hi list,
was playing with FS 1.0.6 and trying to test the registration performance of FS. (Yes I know FS is more suited as a B2BUA, but please read further :p)
So I did the following: - generate one xml file with 20 000 user account like this: <include> <user id="1"> <params> <param name="password" value="1234"/> </params> </user> <user id="2"> <params> <param name="password" value="1234"/> </params> ...
Then I used Sipp to test how many registration per second could be fired to the server (quad core 2.83Ghz). I setup ulimit variables, and disable nat.
I got this: - using SQL Lite: unable to get higher than 80 registrations per second (in fact it's less than this number but didn't test too much this setup), I see a lot of retransmission in Sipp - using SQL Lite in ramdisk (tmpfs): OK with 80 registrations per second but not much - using ODBC and mysql: 130 reg/sec is OK
With ODBC, above 150 reg/sec I see that FS is stalled to 100-110% CPU, I think it's because I'm using only one SIP profile and that SOFIA is monothreaded for this SIP profile. If I'd like to register every 60sec, the server has to support at least more than 300 registration per second.
So I'm wondering if I could setup something like this: - use another SIP Proxy as a registrar and feed the ODBC "sip_registration database" of FS - FS will be able to use this database to setup a call - use FS as the outbound proxy for call routing
But what about the user params that have been setup in the xml file above. I think that FS loads the user params each time a user is registered.
Comments and advices are welcome.
regards, rod.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org