<div>It's on Voyage Linux, a cousin of Debian. I believe it uses glibc.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><br><div class="gmail_quote">On Mon, Jan 28, 2013 at 6:45 PM, Kristian Kielhofner <span dir="ltr"><<a href="mailto:kris@kriskinc.com" target="_blank">kris@kriskinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Out of curiosity does your distro use uclibc, eglibc, or glibc?<br>
<div><div><br>
On Mon, Jan 28, 2013 at 5:41 PM, Jeff Pyle <<a href="mailto: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 </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div></div><br></blockquote></div>