I explicitly set it to 0 for all of my servers. Never had a problem. In my mind setting it to anything different than zero would just be a temporary hack to circumvent a bug in some module, particularly memory leaks.
Various load tests I have made on Apache clearly show that restarting processes has a significant impact on Apache performance. You definitely do not want that to happen too often. On the other hand you are using MPM prefork, so the impact may not be too severe... at least compared to what it would cost to fork new processes to handle load surges. -ascs -----Message d'origine----- De : Grant [mailto:[EMAIL PROTECTED] Envoyé : dimanche 30 septembre 2007 00:35 À : users@httpd.apache.org Objet : Re: [EMAIL PROTECTED] 127.0.0.1 access_log errors > > Ok, thanks Joshua. Do these entries indicate that I might need to > > make a change in my prefork settings? I'm currently using: > > > > StartServers 10 > > MinSpareServers 10 > > MaxSpareServers 20 > > MaxClients 256 > > MaxRequestsPerChild 100 > > No, those log messages rarely indicate any problem at all. But your > MaxRequestsPerChild setting is pretty-low if you are interested in > performance. Ok, would you use 0? I was concerned about a process going haywire eventually. - Grant --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
