[OT] finding memory hungry bits of my code

Andy Armstrong andy at hexten.net
Thu Apr 9 12:40:32 BST 2009

On 9 Apr 2009, at 12:31, Edmund von der Burg wrote:
> I don't think that it is a memory leak - the size tends to remain
> constant after a few requests (it's a webapp - Catalyst under
> mod_perl).
> I reckon that most likely we're doing lots of innocent little bits of
> in-memory caching which all add up to lots of memory getting used. Or
> we're using certain modules that just swell up. Ideally we'd find
> which bits of code lead to the memory being consumed so that we'd get
> a list of places to look at first.

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.

Andy Armstrong, Hexten

More information about the london.pm mailing list