Finally managed to jump from http://serverfault.com/questions/335633/apachemod-wsgi-configuration-for-django-projects-on-a-quad-core to this mailing list.
I am ready to try the switch, already compiled and run mod_wsgi 4.0 on a test machine with the same config as usual. Before going on production I would need to know (Graham I understand you have a full time job at NewRelic so thanks in advance for when you'll have the time to jump on this!) * what are the new mod_wsgi settings for the apache2 conf? what about "listen-backlog" (http://groups.google.com/group/modwsgi/browse_thread/ thread/b6d66d3fe5a53d2c/ what about "blocked-requests" and "blocked-timeout" http://groups.google.com/group/modwsgi/msg/2a968d820e18e97d In Graham's answer to my serverfault question: > if number of processes/threads across Apache child worker processes is less > than 100, the daemon process listener backlog, then all those threads can > also get stuck and you will not know I currently use these settings on a quadcore: <IfModule mpm_worker_module> StartServers 2 ServerLimit 4 MinSpareThreads 2 MaxSpareThreads 4 ThreadLimit 32 ThreadsPerChild 16 MaxClients 64#128 MaxRequestsPerChild 10000 </IfModule> WSGIDaemonProcess subdomain.domain user=www-data group=www-data threads=25 Is this sensible ? After reading http://groups.google.com/group/modwsgi/browse_thread/thread/edffb22b2eac134b and again http://groups.google.com/group/modwsgi/browse_thread/thread/b6d66d3fe5a53d2c/ I see that my threads settings might not be fit... Anything else I'd need to know? -- 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.
