In another thread (http://groups.google.com/group/django-users/ browse_thread/thread/962cfdf7609839eb/),
On Mar 23, 11:48 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > For example, using prefork MPM because PHP is not thread safe in > conjunction with Python web applications in embedded mode in a memory > constrained VPS is a bad idea. You either ditch PHP and use worker > MPM, or you go to mod_wsgi and use daemon mode for the Python web > application. He said it with authority. After perusing his site (in particular, http://www.dscpl.com.au/wiki/ModPython/Articles), it would appear that he speaks from intimate knowledge of the issue. His statement bothered me for two reasons: 1. It was at odds with the Django docs (http://www.djangoproject.com/ documentation/modpython/), which specifically say "you should use Apache's prefork MPM, as opposed to the worker MPM." 2. Because it forced me to confront my own ignorance of exactly *why* prefork MPM is preferred (absolutely required?) over worker MPM. Questions: + What is it about python and/or Django that forces(?) the use of prefork MPM rather than worker MPM? + Does this have to do with python's GIL (global interpreter lock)? + Is there some inherent non-thread-safe aspect of either? Globals? Database caching? + Or is it, as Graham suggests, that it is the combination of PHP and Python that requires prefork? Inquiring minds want to know. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
