<html><head></head><body>If you want to rate-limit traffic below the throughout thresholds of the children, look at the pipelimit module. It would obviate the need for manual htable statekeeping. <br>
<br><br><div class="gmail_quote">On 26 October 2014 15:23:27 GMT-04:00, Alex Balashov <abalashov@evaristesys.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Workers process SIP messages, which means both requests and replies. So, you can't use request-oriented tracking to make that decision. <br />
<br />
The answers to your question are basically:<br />
<br />
1. Keep your call processing as fast and light as possible. <br />
<br />
2. Use async methods. <br />
<br />
Async methods only help so much, due to the strict timing tolerances of SIP, and real-time, delay-sensitive communication in general. The fundamental answer is basically #1--incur as little delay as possible. <br />
<br /><br /><div class="gmail_quote">On 26 October 2014 14:33:43 GMT-04:00, davy van de moere <<a href="http://davy.van.de">davy.van.de</a>.moere@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Gents,<div><br /></div><div>assuming we don't use async methods (I know, it's against fashion), eventually you'll end up in having some bottlenecks in your config... </div><div><br /></div><div>Now thanks to a lot of children you can easily work around this, a maximum of 32 children gives you already quite something, and if you use the dispatcher, you can ramp that up to quite some capacity. ;)</div><div><br /></div><div>Now, there are moments where still limits are passed, so what would be the best way to keep your system healthy?</div><div><br /></div><div>I was thinking in the direction of using a hashtable value or $var to keep track of the children in use and e.g. if 31 children are used, refuse to process the 32th request (assuming 32 children are setup). Would this be a valid strategy? Or am I overthinking? </div><div><br /></div><div>Grtz,</div><div><br /></div><div>Davy </div></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br />sr-users@lists.sip-router.org<br /><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br /></pre></blockquote></div><br />
--<br />
Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. <br />
<br />
Alex Balashov - Principal <br />
Evariste Systems LLC<br />
235 E Ponce de Leon Ave<br />
Suite 106<br />
Decatur, GA 30030<br />
United States<br />
Tel: +1-678-954-0671<br />
Web: <a href="http://www.evaristesys.com">http://www.evaristesys.com</a>/, <a href="http://www.alexbalashov.com">http://www.alexbalashov.com</a><p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br />sr-users@lists.sip-router.org<br /><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br /></pre></blockquote></div><br>
--<br>
Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. <br>
<br>
Alex Balashov - Principal <br>
Evariste Systems LLC<br>
235 E Ponce de Leon Ave<br>
Suite 106<br>
Decatur, GA 30030<br>
United States<br>
Tel: +1-678-954-0671<br>
Web: <a href="http://www.evaristesys.com">http://www.evaristesys.com</a>/, <a href="http://www.alexbalashov.com">http://www.alexbalashov.com</a></body></html>