Hello List.<br><br>I'm currently integrating an IVR in python together with freeswitch using mod_python and ESL and my life has been well until ...<br>The flow of calls went over 80 simultaneous calls.<br>Now freeswitch starts sending packets with huge delays ( even when establishing the call , mainly the 200 ) and firing up the IVR with tons of delay up to 20 seconds.<br>
<br>So i searched the wiki forums and mailing list:<br><br>Put freeswitch on a diet , trimmed modules.conf<br>Played with the ulimit stuff.<br>Played with the IVRS to reduce load to a minimum and i was able to squeeze more 5 calls of performance.<br>
<br>The problem is :<br><br>Top shows <br>top - 16:14:33 up 35 days, 8:15, 3 users, load average: 1.92, 1.76, 1.78<br>Tasks: 133 total, 1 running, 132 sleeping, 0 stopped, 0 zombie<br>Cpu(s): 1.4%us, 3.3%sy, 0.0%ni, 94.6%id, 0.0%wa, 0.3%hi, 0.5%si, 0.0%st<br>
Mem: 8193336k total, 1639156k used, 6554180k free, 177208k buffers<br>Swap: 19534904k total, 0k used, 19534904k free, 1062272k cached<br><br> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND <br>
31361 yadayada 20 0 716m 164m 9628 S 73 2.1 155:17.85 freeswitch <br><br>Freeswitch goes up to 150 % and puff there goes the MOS down to 0.<br><br><br>Some basic System Info :<br>Debian 6.0 ( i heard the timming module is affected by Debian , but if the CPU % gets lower than 95% everything will be more stable)<br>
Python 2.5<br><br>2 x Intel(R) Xeon(R) CPU E5506 @ 2.13GHz<br>8 GB of Ram<br><br>as you can see 94 % of the "Cpu Power" is sleeping :\<br><br><br>It appears freeswitch is only capable of using let's say "one cpu"/thread ??<br>
Do you guys recommend simply starting more instances or redoing the IVR stuff.<br><br><br>Hope you guys can help me out.<br><br>Thanks<br>António Teixeira<br><br><br><br><br><br><br><br><br><br><br><br><br>