Apache Limiter by cPanel

[RaZor Edge]

Seems like I have hard time with my RAM usage on my VPS. On WHM, I have click on "Modify Apache Memory Usage" to see the option offered... but without any confirmation screen, this have been done:

Apache Limiter by cPanel, Inc.
Checking for BSD Accounting ....
Calculating Memory Limit .......2039680..1019840..8193016..375084 5..1920432128..
..640144042..
Largest Webserver child cgi/ssi/php is now limited to 610 meg

610 meg really really high for a VPS with 384meg!!! Should I be concern?

I have search about this function and here's what I found:

Running the WHM option to "Modify Apache Memory Usage" , and re-starting HTTPD to make the new option take effect might at least make what's causing the problem abort when it reaches the memory limit instead of eating all the swap space and crashing the system.

[...]

BTW, what this seems to do is to add the following at the beginning of /etc/httpd/conf/httpd.conf


#-
#Rlimit added by apachelimits.pl
#-
RLimitMEM 202365269
RLimitCPU 240



You can find references to what these do to apache at
http://www.apacheref.com/ref/http_core/RLimitMEM.html
http://www.apacheref.com/ref/http_core/RLimitCPU.html

http://forums.theplanet.com/viewtopic.php?t=12229

[JPC-Veena]

It looks like whm is calculating memory limit for processes based on the memory available for the whole hardware node instead of your vps. It probably does not have a way of detecting you are on a vps. I think you could limit the memory down to what you would like inside the httpd.conf yourself though.

[RaZor Edge]

I think your right. It must calculate for the whole hardware.

I have remove these lines from my httpd.conf as I don't want to break anything...

[coda]

I have had the same problem on my VPS, but not 610MEG - LOL!
For about 6 weeks I was contantly fighting the VPS, services were restarting (and not always successfully) and the server was just SLOOOWWW!

When I check the httpd.conf file, I noticed that entry, and remembered trying that button in WHM. As soon as I removed that line and restarted APACHE the system starting running smoothly. There is always spare memory, and the services have been running reliably ever since.

YES - it seem to look at the entire node - and YES, it can be a huge problem for everyone. This should be disabled in a VPS!

[thisisit3]

I know this is an old thread, but for future reference please look at:

Apache memory limit (RlimitMEM)