<div dir="ltr">On Sun, Sep 28, 2008 at 9:50 PM, Jon Bruel <span dir="ltr"><<a href="mailto:jbr@consiglia.dk">jbr@consiglia.dk</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><font face="Arial" size="2"><span style="font-size: 10pt; line-height: 110%; font-family: Arial;" lang="EN-GB">I have made some load test, where an
Asterisk server was controlled to make a high number of calls to a FreeSWITCH,
which was registered on Asterisk. Each had its own server. The calls made to
the FreeSWITCH were answered and echoed. The CPU load on the FreeSWITCH server
approached 100 % at around 100 calls. Similar test with an Asterisk server
would show 2-3 times less CPU load. Looping back to the Asterisk, thus avoiding
a possible CPU-loading application (echo), did not show a significantly different
result.</span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; line-height: 110%; font-family: Arial;" lang="EN-GB">The test has been done on a CentOS 4
and a FC8 with similar result. </span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; line-height: 110%; font-family: Arial;" lang="EN-GB">Any hints about how to increase the
capacity to the level of several times the level of Asterisk – as reported
by others? Are we possibly dealing with some hardware issues related to the NIC
and its drivers. /Jon</span></font></p></div></div></blockquote><div>yes, we need more information to be able to help you<br><br>which protocol? SIP, I presume, then paste your profiles and also the dialplan you are using<br>
<br>you can pastebin it all<br><br>configs<br>proc/cpuinfo<br>proc/interrupts<br>free<br>ip addr<br>dmesg<br><br>freeswitch start up log<br>freeswitch debug log for a SINGLE call<br><br>etc, etc<br><br></div></div><br>-- <br>
wasim h. baig | principal consultant | convergence pk | +92 300 8508070 | as you scope creep, so shall we reap ... <br>
</div>