I just updated from repo.profhost.eu. 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%.

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%.

That's great, but does it make any sense?

Does an rtp-timer-name of 'none' pose any risks?

- Jeff

On Mon, Jan 28, 2013 at 8:43 PM, Jeff Pyle <jpyle@fidelityvoice.com> wrote:

It's on Voyage Linux, a cousin of Debian. I believe it uses glibc.

- Jeff

On Mon, Jan 28, 2013 at 6:45 PM, Kristian Kielhofner <kris@kriskinc.com> wrote:

Out of curiosity does your distro use uclibc, eglibc, or glibc?

On Mon, Jan 28, 2013 at 5:41 PM, Jeff Pyle <jpyle@fidelityvoice.com> wrote:
> Hello,
>
> I'm running HEAD version from Jan 22 on an Alix board with an AMD Geode LX
> processor (i386). I can sustain 30 concurrent calls averaging around 70%
> CPU utilization by the freeswitch process, measured by top. Bypass media
> and proxy media are disabled. PCMU is forced on both endpoints (no
> transcoding).
>
> The problem is the RAM usage over time. The board has 256M. Idle,
> freeswitch occupies around 4% after a fresh restart. A minute or so after
> 30 calls are nailed up the RAM usage is about 7.2%. After 5 minutes, 13.6%.
> After 60 minutes, near 65%. Disconnecting the calls returns the RAM usage
> to 6-8%.
>
> I've not tried to troubleshoot an issue like this before. Is valgrind the
> next step, or would something else make more sense?
>
>
> Regards,
> Jeff