Sorry, I was wrong. MaxSpareServers is only available in the prefork MPM module. Windows binaries on the other hand are compiled with mpm_winnt: http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html Look up MaxMemFree, MaxRequestsPerChild, ThreadLimit, ThreadsPerChild directives. All of these are available in mpm_winnt and allow you to fine tune Apache's memory consumption. Thanks for your question, though. At least, today I've learnt some new stuffs about Apache. :D Regards, MegaBrutal 2010/8/20 MegaBrutal <megabrutal@xxxxxxxxx>: > Hello, > > Read this document: > http://httpd.apache.org/docs/2.2/misc/perf-tuning.html > > My guess is that child processes consume extra memory, as the server > creates them when there are many clients connected simultenously. Note > that it's a perfomance optimization: child processes will be there > ready to handle clients when they arrive as soon as possible. Though > you could control how many child processes may hang around idle with > the MaxSpareServers directive: > http://httpd.apache.org/docs/2.2/mod/prefork.html#maxspareservers > > Note that if you really restrict that, the server may lose performance > (ie. get slower), because then it needs to create the necessary child > processes when clients connect. > > It's also possible that Apache caches some files those requested > pretty often, but AFAIK this feature is not on by default so you must > have manually configured it, so most likely you would know about it > then. > > Regards, > MegaBrutal > > > 2010/8/20 Pravesh Rai <pravesh.rai@xxxxxxxxx>: >> Hi All, >> >> Found that, on Windows x86 & x64 setup, memory consumption (by >> httpd.exe) gets increased with time, under stress conditions. Is there way, >> through configuration settings, to control this resource usage ? >> >> Thanks, >> PR > --------------------------------------------------------------------- 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
|