So we have a situation where keep=alive connections are not being used effectively by client applications (i.e. subsequent requests on keep-alive connections are not frequent enough to keep Apache workers busy all the time, resulting in low CPU utilisation). At the same time, because there are already so many keep-alive connections, the server is not accepting any more new connections from the client application.
Thus, the server is mostly idle but not accepting new connections. Does reducing the KeepAliveTimeOut sound like a good option in this case? Could you also elaborate on the statement --- With event, keep alive connections don't tie up a thread between requests. Does that mean a thread is allotted per connection, rather than per request in case of keep-alive connections (thus essentially mimicking a worker MPM rather than an event MPM)? Thanks, Raj On Tue, Nov 4, 2014 at 4:25 PM, Eric Covener <cove...@gmail.com> wrote: > On Tue, Nov 4, 2014 at 11:23 AM, Eric Covener <cove...@gmail.com> wrote: > > No, with event, keepalive connections don't tie up a thread between > requests. > > Sorry, I see what you mean. Yes, each process will stop calling accept > out of fear that too many keepalive connections may become active (and > hence be queued). Each process does this in case other processes are > not similarly bogged down. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > -- @BlisMedia <http://twitter.com/BlisMedia> www.blismedia.com <http://blismedia.com> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of BlisMedia Ltd, a company registered in England and Wales with registered number 06455773. Its registered office is 3rd Floor, 101 New Cavendish St, London, W1W 6XH, United Kingdom. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.