J
Jaap Karssenberg
Does anyone know of a simple way to see where the memory goes in a large
perl application ?
perl application ?
C
ctcgag
Jaap Karssenberg said:
Depends on how modular the application is.
Xho
J
Jaap Karssenberg
On 10 Feb 2004 01:18:10 GMT (e-mail address removed) wrote:
: > Does anyone know of a simple way to see where the memory goes in a
: > large perl application ?
:
: Depends on how modular the application is.
It's kinda modular, if can figure out the memory usage per module that
would make a good start for further analysis. So what do you suggest ?
: > Does anyone know of a simple way to see where the memory goes in a
: > large perl application ?
:
: Depends on how modular the application is.
It's kinda modular, if can figure out the memory usage per module that
would make a good start for further analysis. So what do you suggest ?
B
Ben Morrow
Jaap Karssenberg said:
Devel::Leak may help.
Ben
C
ctcgag
Jaap Karssenberg said:
When I have no idea where the memory could be going, usually I already have
a driver for each module, so I just rig it up to run a psuedo-workload on
each module separately and check the mem usage using "top" or whatever.
But I am proud (or perhaps ashamed) to say I've used Acme::Abuse to run
each module (in turn) in a separate interpreter, and just compared the
sizes of the respective processes, when I wasn't able to readily make a
realistic driver.
But the thing I most often use is just Data:
umper, as usually there areonly a handful of suspects as to where the memory could be going.
warn "suspect1 is ",length Dumper(\%suspect1); # give rough estimate of
size
Xho