[mod_python] mpm-worker and mod_python

Graham Dumpleton graham.dumpleton at gmail.com
Sun Apr 8 21:44:51 EDT 2007

On 08/04/07, Andres Morey <amorey at octopart.com> wrote:
> Hi,
> I had mod_python 3.3.1 running on Apache 2.2.4 with mpm-prefork (on
> Ubuntu 6.10 x86_64). mod_python wasn't caching modules so I
> recompiled apache with mpm-worker instead.

mod_python should be caching modules with prefork. On what basis do
you believe it isn't? Are you possibly not reading the Apache error
log messages properly where it clearly gives the process ID for which
process is currently loading mod_python modules. For prefork there can
be many Apache child processes so you will see for each distinct
module a loading message for each distinct process.

> Now mod_python is caching
> modules but apache is taking up 100% of system resources.

What did you do to trigger the condition? Does it do that as soon as
Apache starts, or only after the first request that triggers some
mod_python code?

> Is it
> possible to cache modules with Apache using mpm-prefork?

It should work fine now.

BTW, what modules are you talking about? Are you talking about modules
installed as part of Python, or those in your document tree and
containing a handler or which are being loaded by

Is your mod_python code otherwise working? There is a rare case where
an issue with md5 hash library in PHP may cause a lot of problems with
the new module loaded in mod_python 3.3.1.


More information about the Mod_python mailing list