Thank you for the reply, Andre. I now understand how setting KeepAlive to On would improve the performance of a website (The Apache manual says that a 50% increase in throughput could be expected). So I changed the KeepAlive to On and restarted the server.
I however wonder if this will fix the issue. The reason being, I haven't changed the website code at all the past few months and there hasn't been any increase in the website traffic too. Hence I am unable to understand why we are suddenly seeing an increase in the number of httpd processes. The only thing I changed is the session-timeout value from 30 minutes to 240 minutes. Thanks, Joe On Mon, Oct 5, 2009 at 1:04 PM, André Warnier <a...@ice-sa.com> wrote: > Joe Hansen wrote: >> >> Rainer, >> >> Here are the KeepAlive values in httpd.conf: >> >> KeepAlive Off >> MaxKeepAliveRequests 100 >> KeepAliveTimout 15 >> > Well, since you have "KeepAlive Off", the other 2 do not matter. > But as such, it means that each request of each browser is going to create a > new connection to the webserver, just for that one request. > So if there is a page with 10 <img> links inside, you will end up > establishing (and tearing down) a total of 11 TCP connections (one for the > main page, one each for each <img>). > That may or may not have a bearing on the situation you are seeing. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
