[OT] finding memory hungry bits of my code

[Mark Morgan]

On Thu, Apr 9, 2009 at 12:40 PM, Andy Armstrong <andy at hexten.net> wrote:
> That sounds as if it could just be Perl getting up to cruising (memory)
> altitude. Perl isn't especially keen on giving memory back to the OS once
> it's used it; instead it keeps it hanging around and uses it to satisfy
> future allocations.

You beat me to that.

Also, depending how you're viewing the memory usage, and the OS that
you're under, you may be including a lot of COWed shared memory
multiple times.  I've found that Linux in particular is quite opaque
when trying to determine how much memory is shared, when using
mod_perl.

Mark.