When you max out this number, you get no more instances - no more connections until you have more available. When you hit this ceiling it's a hard ceiling, the end viewer gets a failure to connect error. So, whatever you do you'll want to make sure you have more resources than visitors. An inefficient application can waste instances and keep their tied up for longer periods of time. People serving simple website page views seldom have a problem.
Like I said, the math here is more complex than ServerLimit/MaxClients * X = Y.
On 4/17/10 1:40 AM, Brent Clark wrote:
HiyaWhat is the consequences of an overly increased ServerLimit and MaxClients. And to add to this puzzle. What if the number of apache process reach that limit.Kind Regards Brent Clark ---------------------------------------------------------------------The official User-To-User support forum of the Apache HTTP Server Project.See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
-- Jason A. Nunnelley +1 2562971652 http://www.google.com/profiles/imjasonn [Member Tekany, LLC] --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx