Re: Pre fork or worker MPM

Generally, mpm worker is more preferable, but there is one more thing: in which mode will you use mod_wsgi ? Embedded or daemon-mode ? I'd suggest you to read mod_wsgi main page first. On Wed, May 18, 2011 at 1:15 AM, ydjango wrote: > I am using Python 2.5, d

Re: Pre fork or worker MPM

On Tue, May 17, 2011 at 6:00 PM, ydjango wrote: > I remembered reading this long back - "Django requires Apache 2.x and > mod_python 3.x, and you should use Apache’s prefork MPM, as opposed to > the worker MPM." That statement dates back to when Django wasn't threadsafe (so we're talking pre-1.0

Re: Pre fork or worker MPM

Thank you, I remembered reading this long back - "Django requires Apache 2.x and mod_python 3.x, and you should use Apache’s prefork MPM, as opposed to the worker MPM." I was not sure if prefork is required because of some limitation (like threading issues) in Django 1.1 or python 2.5 or was it b

Re: Pre fork or worker MPM

On Tue, May 17, 2011 at 4:15 PM, ydjango wrote: > I am using Python 2.5, django 1.1 with mod_wsgi 2.5 > > Does it matter if I use prefork or worker MPM for apache? In general, worker will use less RAM, thus allowing higher concurrency and usually higher perceived performance. But take that sugge

Re: Pre fork or worker MPM

Hello ydjango, On Tuesday, May 17, 2011 2:15:37 PM UTC-7, ydjango wrote: I am using Python 2.5, django 1.1 with mod_wsgi 2.5 > > Does it matter if I use prefork or worker MPM for apache? > > Which one is recommended for production use? Which one you choose depends on what you are trying to ac

Pre fork or worker MPM

I am using Python 2.5, django 1.1 with mod_wsgi 2.5 Does it matter if I use prefork or worker MPM for apache? Which one is recommended for production use? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to dja