Rod - interesting. I am also thinking about the best architecture as far as registrations goes.<br><br>So things that spring to my mind include:<br><br>- using more that one FS box to spread the load - basically create a FS cluster - with OpenSIPS in front to load balance<br>
- use <i>mod_xml_curl </i>to pull /directory info from one source<br>- possibly using OpenSIPS to handle registrations (although I am not sure how to get around the single point of failure issue there) <br><br><br><br><div class="gmail_quote">
On Mon, May 3, 2010 at 9:39 AM, Rod. <span dir="ltr"><<a href="mailto:kawarod@laposte.net">kawarod@laposte.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi list,<br>
<br>
was playing with FS 1.0.6 and trying to test the registration<br>
performance of FS. (Yes I know FS is more suited as a B2BUA, but please<br>
read further :p)<br>
<br>
So I did the following:<br>
- generate one xml file with 20 000 user account like this:<br>
<include><br>
<user id="1"><br>
<params><br>
<param name="password" value="1234"/><br>
</params><br>
</user><br>
<user id="2"><br>
<params><br>
<param name="password" value="1234"/><br>
</params><br>
...<br>
<br>
Then I used Sipp to test how many registration per second could be fired<br>
to the server (quad core 2.83Ghz).<br>
I setup ulimit variables, and disable nat.<br>
<br>
I got this:<br>
- using SQL Lite: unable to get higher than 80 registrations per<br>
second (in fact it's less than this number but didn't test too much this<br>
setup), I see a lot of retransmission in Sipp<br>
- using SQL Lite in ramdisk (tmpfs): OK with 80 registrations per<br>
second but not much<br>
- using ODBC and mysql: 130 reg/sec is OK<br>
<br>
With ODBC, above 150 reg/sec I see that FS is stalled to 100-110% CPU, I<br>
think it's because I'm using only one SIP profile and that SOFIA is<br>
monothreaded for this SIP profile.<br>
If I'd like to register every 60sec, the server has to support at least<br>
more than 300 registration per second.<br>
<br>
So I'm wondering if I could setup something like this:<br>
- use another SIP Proxy as a registrar and feed the ODBC<br>
"sip_registration database" of FS<br>
- FS will be able to use this database to setup a call<br>
- use FS as the outbound proxy for call routing<br>
<br>
But what about the user params that have been setup in the xml file<br>
above. I think that FS loads the user params each time a user is registered.<br>
<br>
Comments and advices are welcome.<br>
<br>
regards,<br>
rod.<br>
<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>