memory usage in mod_perl

Bradley Baetz bbaetz at
Tue Jan 16 20:20:52 UTC 2007

On 17/01/07, David Miller <justdave at> wrote:
> So we knew memory usage was going to be higher with mod_perl enabled,
> but this is a little ridiculous. :)

It shouldn't be higher. It should be less because the various perl
modules are preloaded and shared.

> So b.m.o ran fine for a week or two after enabling mod_perl, but it's
> had to be rebooted twice in the last 3 days because it plain ran out of
> memory.  It's got 4GB on it with 2GB swap.

Add a hook that checks the process memory and exits if its more than a
certain amount? ;)

> Most of the httpd processes are staying in the 30 to 50 MB range for RAM
> usage (which is about what we expected).  But we eventually get more and
> more of them that start using up 350MB and even up to 635MB of RAM for
> the one listener.  Some of these happen within a few minutes of
> rebooting.   The problem comes when we start getting lots of requests at
> once so it starts adding listeners.

How big were they before mod_perl? For the 30-50MB ones, how much is
shared with other processes?

> If anyone has any ideas where to look or how to debug it, that'd be
> great, but it kinda smells like something's leaking.

Apache::Status, with appropriate B:: modules installed. Add some
logging to check that the cleanuphandler is being run


More information about the developers mailing list