<div dir="ltr">Thanks for your response.<br><br>We realized that with 200 children the problem is still happing.<br><br>We are using db ( MySQL 5 ) in every request in the config file through the following modules:<br><br>
- lcr: to check every request where come from<br><br> - dispatcher: to make load balancing with a pool of asterisk in cluster<br><br> - avpsops: to use some user preferences<br><br> - carrieroute: to balance outbound calls to several providers<br>
<br>Is this a high load of db transactions to the openser?<br><br>Regards<br><br><br><div class="gmail_quote">2008/9/3 Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Increasing the number of children to 200 will not help.<br>
Most likely, your config is doing something 'wrong' or being terribly<br>
intensive on mysql db.<br>
Openser is very light and it can handle lot's of transaction, but if<br>
you are using a slow db and you are doing db queries during your<br>
transaction processing, then your server will be slow.<br>
<br>
Check your config and see what's going 'wrong' there.<br>
<br>
As a reference, openser is able to do 150 cps using a single child and<br>
the CPU is barely utilized (on a slow machine).<br>
<br>
<br>
Regards,<br>
Ovidiu Sas<br>
<div><div></div><div class="Wj3C7c"><br>
On Wed, Sep 3, 2008 at 10:31 AM, Samael - <<a href="mailto:samael.zgz@gmail.com">samael.zgz@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
><br>
><br>
> We are deploying OpenSER in a large infrastructure together with Asterisk to<br>
> support thousands of current transactions.<br>
><br>
> We are using udp listener and mysql module in openser.<br>
><br>
><br>
><br>
> We had to increase the children parameter of the openser.cfg to 200 because<br>
> Openser couldn't handle the high amount of concurrent SIP REQUESTs from<br>
> ASTERISK (Not only INVITES, but also a lot of SIP OPTIONs), that means that<br>
> Openser couldn't handle more than 'children' REQUEST loosing the rest of the<br>
> concurrent REQUEST.<br>
><br>
> children=200<br>
><br>
><br>
><br>
> But then, the following error appeared in the openser:<br>
><br>
> ERROR:mysql:db_mysql_new_connection: driver error: Too many connections<br>
><br>
><br>
><br>
> This is because the Standard parameter of mysql "max_connections" is set to<br>
> 100.<br>
><br>
><br>
><br>
> In mysql CLI, we can see that every child process of openser has a mysql<br>
> connection. (see in Mysql> SHOW PROCESSLIST)<br>
><br>
><br>
><br>
> The recommended max_connections parameter is 500-1000 => we have a limit of<br>
> 500-1000 concurrent SIP REQUEST to be processed by the openser.<br>
><br>
><br>
><br>
> Why there is a process for every child?<br>
><br>
><br>
><br>
> Why is neccesary a mysql connection for every child?<br>
><br>
> Can the openser have a pool of mysql connection to be used by thousands of<br>
> children?<br>
><br>
> Regards<br>
><br>
</div></div>> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.kamailio.org">Users@lists.kamailio.org</a><br>
> <a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
</blockquote></div><br></div>