>>> apache MaxClients has been lowered to 50 which is a shame because I >>> have 30+ separate images on each of my pages and that number can not >>> be reduced. This means I may not be able to serve more than 1 full >>> page at a time. >> >> This is wrong. > > Agreed. From TFM; "The MaxClients directive sets the limit on the > number of simultaneous requests that will be served" and i'd say when > they say "requests", they're talking about TCP sessions. So in the old > days of HTTP/1.0 you'd be right, and if you'd turned off pipelining > (KeepAlives) you'd be right. > > The default for MaxKeepAliveRequests is 100, so no problems > downloading the 30+ objects within a single session, assuming you have > KeepAlive on.
I'm trying to figure out the maximum number of apache2 processes that could run simultaneously according to my config so I don't run out of memory again. I have KeepAlive on, but I can see in the log that a different pid serves each file associated with a particular page request. Doesn't that mean a different apache2 process is serving each file and I need one process for each file served at any particular moment? How does KeepAlive relate to the number of running apache2 processes? - Grant
