That sounds like a great start. To start refining things more gets a lot harder unfortunately.
I was working on some inbuilt performance metrics monitoring for mod_wsgi but it is still stuck out on a branch and I haven’t gone back and merged the changes to main working branch. If we had that then we could start to look more closely at per request CPU utilisation and impacts of the GIL by comparing that to process wide CPU utilisation. Other metrics those changes provide such as capacity utilisation could help dial in the best configuration even more. I really need to get back to checking the state of that work and merging it back in. > On 16 Mar 2016, at 12:36 AM, Lars Westermann <[email protected]> wrote: > > Hi Graham > > Thank you for your very valuable comments and suggestions. They are MUCH > appreciated! > > We ended up building a new server (Ubuntu 14.04) with apache 2.4.7 and custom > built mod_wsgi 4.4.21 (along with php-fpm). > For our backend we tuned the ldap servers (increased the cache size) and put > pgbouncer in front of our postgresql databases. > > By using your suggested webserver configuration (10 processes, 3 threads > each) we are able to handle much more than we need to handle - > in fact our performance went up by a factor 40 or more. Now the cpu-load-1 in > busy hour averages around 0.1-0.2, where it > previously would be around 2.5. Now cpu-load is more in line with > cpu-utilization which we were aiming at. And we are > handling 20-30 reqs/sec 50% of the time, and 30-50 reqs/sec 20% of the time - > so that looks really great. And the cpu-usage > has switched from being spent in apache to mod_wsgi. We haven't seen > cpu-usage above 20% > > Best Regards, > Lars -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
