On 9/26/06, <b class="gmail_sendername">Steven</b> <<a href="mailto:critch@basesys.com">critch@basesys.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No, apache won't die. Apache will stop answering new requests till a<br>child process is able to process the request. </blockquote><div><br>Steven makes an important point here -- Apache has some tunable parameters that allow you to set it's behavior, depending on your circumstances. In the case of Asterisk, we should have a couple of knobs we can tweak to control how Asterisk handles a high number of incoming connections, whether they're just a traffic spike or a DoS attack.
<br><br>I know that other VoIP vendors claim they can handle X number of invalid connections per second while still keeping all the legitimate calls working -- I'd obviously like to see Asterisk do the same (for reasonable values of X, of course). Unfortunately, in the limited load testing I've done with Asterisk (specifically in the SIP channel), when you start to send more than a few incoming calls per second, Asterisk starts to freak out; namely, it responds to the wrong packets, sends multiple replies, and/or crashes.
<br><br>I know I talked to several people about this at VON -- does anybody have a lead on some good high-end VoIP call generators we can use to test Asterisk and make it better?<br> </div>-Jared<br></div>