Re: [modwsgi] Concurrent requests clogs single apache process

When you say "load test", do you mean totally overload the server way beyond the realistic amount of traffic you would ever expect to get? :-) In other words, are you running tests like: ab -c 15 -n 10 http://mysite or: siege -c 15 -t 120s http://mysite

Re: [modwsgi] Concurrent requests clogs single apache process

Oh, and I did not have any MPM settings set in Apache configuration. I tried adding what you sent and it didn't have an effect. Thanks so much for helping me out! On Thursday, September 17, 2020 at 2:14:37 PM UTC-4 Scott McConnell wrote: > My load test is pretty mellow, I thought... > >

Re: [modwsgi] Concurrent requests clogs single apache process

My load test is pretty mellow, I thought... Originally was doing: ab -c 15 -n 500 -s 10 https://mysite.com/ And this caused response times of ~8 sec Trying again with: ab -c 5 -n 500 -s 10 https://mysite.com/ still leads to ~3 sec response time. My hope was for this to be able to handle ~100

Re: [modwsgi] Concurrent requests clogs single apache process

One question. Given you are using a quite old version of Apache, what version of mod_wsgi are you using? If you are using a really old version of mod_wsgi, and are returning absolutely huge responses, the large child worker processes sizes could be because you are triggering some behaviour in

Re: [modwsgi] Concurrent requests clogs single apache process

I am using mod_wsgi/4.5.17. I haven't made any drastic changes to the server... I hadn't touched /etc/apache2/apache2.conf until talking to you. I haven't done much other than what's outlined here

Re: [modwsgi] Concurrent requests clogs single apache process

That version of mod_wsgi is over 3 years old.There has been almost 20 releases since then. I checked back regarding the buffering workaround and it predates that version, and actually seems to only be absolutely necessary with Apache 2.2. If you run a single request on the URL which is slow,