2009/11/29 peter2108 <[email protected]>: > I am developing a Django site on Webfaction servers. It will be low > traffic but have quite a few Django apps. I'm using mod_wsgi in > embedded more. When I save a new version of a .py file I restart the > Apache server. This server only supports Django. In fact the static > media Django needs are served by Webfactions main server. > > I have read on this list and in the docs that one reason for using > daemon mode is that it all you need to update the Pythin files being > used is to 'touch' the wsgi script which will be faster than > restarting the Apache server. In my set up this is not an issue - it > takes about 3secs to restart the server. > > The only issue I face is memory usage - accounts on Webfaction have > 40, 80, 120, 160Mb memory limits and it is possible to bump into these > whereupon your process is bumped of and you get an admonition email > telling you to fix things. > > So will daemon mode use more or less memory, and is the gain (if there > is one) worth switching to the more complex daeomon set up?
What have you set: StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 to and is your Apache using worker or prefork MPM? How big is a single Apache server child process when Django application is loaded and levelled out at its maximum memory usage? Graham -- 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.
