Thank you very much for all replies. We're investigating the issue in our dev environment with all your notes taken into account. We don't use Cache::FastMmap. Suspected handlers heavily use Coro/AnyEvent. I'll write about results once we have finished.

Cheers
Eugene

----- Original Message ----- From: "Cees Hek" <cees...@gmail.com>
To: "William T" <dietbud...@gmail.com>
Cc: "Eugene Toropov" <j...@aaanet.ru>; <modperl@perl.apache.org>
Sent: Thursday, October 07, 2010 3:06 AM
Subject: Re: huge apache+mod_perl processes


Also, if you are using something like Cache::FastMmap, your processes
will look quite large depending on the size of your cache, but this
memory is shared between children so it is not that big a deal.  From
the docs:

-----
Because Cache::FastMmap mmap's a shared file into your processes
memory space, this can make each process look quite large, even though
it's just mmap'd memory that's shared between all processes that use
the cache, and may even be swapped out if the cache is getting low
usage.
-----

Not sure if you are using this module, but it could explain your
process size jumping up by a large amount, but not growing
significantly after that.

Cheers,

Cees

On Wed, Oct 6, 2010 at 5:49 PM, William T <dietbud...@gmail.com> wrote:
If you don't have an unbounded growth issue it is likely do to some
library pulling in alot of dependencies or the creation/caching in
memory of some large data structure. You can preload all the
offending libraries and see if that causes a jump in the initial
memory allocation for you apache procs. If not you can create a
Handler that fires during cleanup/log phase to capture memory size
right after each access.

2010/9/29 Eugene Toropov <j...@aaanet.ru>:
Greetings,

We have a problem with huge Apache+mod_perl2 processes of 150-200 Mb in
size. After apache restart they are usually 40-50 Mb in size, then in a
minute grow up to 100-150 Mb and then some time later may grow up to 200 Mb. I suspect a certain type of http queries and would like to know if there are
any manuals/howtos/tools to investiagate such cases.


Reply via email to