[OT] finding memory hungry bits of my code
astle at lokku.com
Fri Apr 10 13:27:50 BST 2009
If there is something out there that does for perl memory usage analysis
what NYTProf does for profiling, then I am >dying< to get my grubby
little hands on it.
My ideal tool would give me a breakdown of the memory used by current
SVs by package. Not sure if I'm saying that right or if this is even
The problem I seems to face twice a year is that some hash somewhere
that is declared in package scope or in the lexical scope of a file is
being used as a cache and that cache's size is getting too big. I don't
know of a programatic way to identify the problem hash.
Anybody know of a magic tool that does what I'm after? Or maybe you
know of a way to walk all things declared in package scope or the
lexical scope of a file?
More information about the london.pm