I've been running django (trunk and M-R) on apache prefork with no problems.  I recently switched to the worker MPM, and so far, everything seems to work fine (with better memory usage, I might add).  I did have a problem on a separate installation, however, related to memcache.  I think there may be a deadlock problem when using memcache and the worker MPM, but I haven't investigated it much yet.
But I can confirm that this combination works for me:
FreeBSD 6.0
Apache 2.0.55 with worker mpm
python 2.4.3
mod_python 3.2.8
psycopg 1.1.21
postgresql 8.1.3


On 4/21/06, Richie Hindle <[EMAIL PROTECTED]> wrote:


[Jacob]
> I'd suggest switching to the "prefork" MPM for Apache

For what it's worth, I think this advice should be in the documentation.
The documentation says "Apache with mod_python currently is the preferred
setup for using Django on a production server" but it doesn't explain
which MPM.

--
Richie Hindle
[EMAIL PROTECTED]




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to