Just acknowledging that I know I haven't answered this yet. Very little time to deal with non work stuff right now and have limited Internet access as well. Will try and answer it over the coming weekend.
Graham On 8 February 2011 09:31, stipa <[email protected]> wrote: > Hi, > > I am trying to find a best configuration for my system. I have a > dedicated machine that hosts heavy python app, that uses apache + > django + mod_wsgi. No other components (php, static files) are hosted > there. Unfortunately the python app is not thread safe, and I cannot > use thread based request handling - neither mpm prefork with threads > or wsgi in daemon multithreaded mode. > > I read in many sources that mod_wsgi is best to use in daemon mode, > however in my case I would have to do something like: > >> WSGIDaemonProcess lol processes=25 threads=1 display-name=lol > > I see no bonuses in using wsgi daemon + mpm prefork: > > 1) WSGI creates processes in same process group. Not sure, however, if > it gives me any advantages. Taking into account that machine is only > hosting this python app, I think it makes no odds. > 2) In this particular configuration 25 threads will be created at > startup. However, with "StartServers" prefork option I have the same. > 3) I can "touch" .wsgi file in order to reload app, no need to restart > apache. Well, yeah. > > So the question is - does it make sense for me to use wsgi daemon + > mpm worker, or wsgi embedded + mpm prefork will give me same > performance / memory footprint? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
