<div><div>Version:</div><div> FreeSWITCH version: 1.3.4-n20130122T122521Z-1~squeeze+1 (-n20130122T122521Z-1~squeeze+1)</div></div><div><br></div><div>The calls are bridged, from one sofia profile to another.</div><div><br>
</div><div>Unfortunately two concurrent calls doesn't seem to trigger the same behavior.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><br><div class="gmail_quote">On Mon, Jan 28, 2013 at 11:21 PM, Ken Rice <span dir="ltr"><<a href="mailto:krice@freeswitch.org" target="_blank">krice@freeswitch.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="Monaco, Courier New"><span style="font-size:11pt">Ok the package timestamps/versions there don’t do us a lot of good, we need to know the version line from the FreeSWITCH CLI..<br>
<br>
<br>
On 1/28/13 9:59 PM, "Jeff Pyle" <<a href="http://jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>> wrote:<br>
<br>
</span></font><blockquote><font face="Monaco, Courier New"><span style="font-size:11pt">I just updated from <a href="http://repo.profhost.eu" target="_blank">repo.profhost.eu</a> <<a href="http://repo.profhost.eu" target="_blank">http://repo.profhost.eu</a>> . The most recent timestamp on the packages was 2013-01-28 03:41:21 GMT. Same behavior. At 5 minutes it was using 12.5% RAM. At 40 minutes, 60.4%. After disconnecting the calls the usage returned to 8.5%.<div>
<div><br>
<br>
I started toggling config items to see if I could impact this. I found one that seems to have an effect: rtp-timer-name in the sofia profile config. By changing it from 'soft' to 'none', the CPU utilization with 30 calls dropped from ~70% to ~46%, and the RAM usage is rock solid at 5.8%.<br>
<br>
That's great, but does it make any sense?<br>
<br>
Does an rtp-timer-name of 'none' pose any risks?<br>
<br>
<br>
<br>
- Jeff<br>
<br>
<br>
<br>
On Mon, Jan 28, 2013 at 8:43 PM, Jeff Pyle <<a href="http://jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>> wrote:<br>
</div></div></span></font><div><div><blockquote><font face="Monaco, Courier New"><span style="font-size:11pt">It's on Voyage Linux, a cousin of Debian. I believe it uses glibc.<br>
<font color="#888888"><br>
<br>
- Jeff<br>
</font><br>
<br>
On Mon, Jan 28, 2013 at 6:45 PM, Kristian Kielhofner <<a href="http://kris@kriskinc.com" target="_blank">kris@kriskinc.com</a>> wrote:<br>
</span></font><blockquote><font face="Monaco, Courier New"><span style="font-size:11pt">Out of curiosity does your distro use uclibc, eglibc, or glibc?<br>
<br>
On Mon, Jan 28, 2013 at 5:41 PM, Jeff Pyle <<a href="http://jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>> wrote:<br>
> Hello,<br>
><br>
> I'm running HEAD version from Jan 22 on an Alix board with an AMD Geode LX<br>
> processor (i386). I can sustain 30 concurrent calls averaging around 70%<br>
> CPU utilization by the freeswitch process, measured by top. Bypass media<br>
> and proxy media are disabled. PCMU is forced on both endpoints (no<br>
> transcoding).<br>
><br>
> The problem is the RAM usage over time. The board has 256M. Idle,<br>
> freeswitch occupies around 4% after a fresh restart. A minute or so after<br>
> 30 calls are nailed up the RAM usage is about 7.2%. After 5 minutes, 13.6%.<br>
> After 60 minutes, near 65%. Disconnecting the calls returns the RAM usage<br>
> to 6-8%.<br>
><br>
> I've not tried to troubleshoot an issue like this before. Is valgrind the<br>
> next step, or would something else make more sense?<br>
><br>
><br>
> Regards,<br>
> Jeff <br>
</span></font></blockquote></blockquote></div></div></blockquote></div><br></blockquote></div><br>