On 6/4/07, Arnab Ganguly <aganguly01@xxxxxxxxx> wrote:
Hi All, I was referring to http://httpd.apache.org/docs/2.0/misc/perf-tuning.html and the below paragraph is a snippet from the given url I am not clear about the which memory leaks it is referring.I have highlighted that part. Related to process creation is process death induced by the MaxRequestsPerChild setting. By default this is 0, which means that there is no limit to the number of requests handled per child. If your configuration currently has this set to some very low number, such as 30, you may want to bump this up significantly. If you are running SunOS or an old version of Solaris, limit this to 10000 or so because of memory leaks. Can somebody explain me the above memory leaks?Is it fixed in the Apache2.2 onwards release, also in case of Linux OS do we need to follow the same procedure as that of SunOS for the param MaxRequestPerChild.
It can't be fixed in an apache version because it is a bug in the OS libraries, not in apache. There are no known memory leaks in apache, but if you are using leaky libraries (via php, mod_perl, etc) or your OS has leaks in its base libraries, then over time apache may use more an more memory. By flushing the processes every now and then, this problem is mitigated. I believe that you won't see the OS leak problem on any modern OS (including Linux) so you can leave MaxRequestsPerChild at 0. If you find that memory usage is increasing without bound (perhaps because of some third-party library) then you can always go back and reset it. Joshua. --------------------------------------------------------------------- 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
|