On Tuesday, September 07, 2004 6:38 PM
Duarte Cordeiro
a) Buy more RAM.
The server has 6GB Ram, and the VM 400MB. I can easily ask for a increment on the VM, but how am I going to explain to the admins, that this webserver, serving 100 users (not concurrent users) needs more than 400MB of ram (only for running apache)?
Let's calc: You've got 400 Megs. Say, 40 Megs are in use by the system. The remaining 360 Megs allow 360/20 = 18 requests coming in at the same time, and -boom- off goes the RAM. This is because Apache when being armed with mod_perl pre-loads every perl script used. Ie., every instances carries a complete and whole OTRS installation and code with itself.
c) Switch to another MPM, say 'worker': <IfModule worker.c> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 </IfModule>
I have both sections uncommented. How do I know which MPM is being used?
I guess Apache was installed as an RPM, so I guess the standard MPM Prefork was used. This would allow later loading of PHP, which isn't possibly with the Worker MPM. So, use your software package management software to switch the Apache version used from mpm_prefork to mpm_worker. The software will tell you which one is installed. Something like this should do so, too, iirc: # rpm -qa | grep apache
d) Disable any module not needed, esp. mod_php4 don't have any line with LoadModule mod_php4 or similar.
modules/enabled and stuff?
e) Disable Apache::Reload in apache2-perl-startup.pl that line doesn't exists in my file:
Sorry, it's scripts/apache2-httpd.include.conf With kind regards, Robert Kehl -- Erste Pass, gleich Scheiße! Dragoslav Stepanovic (beim ersten Training nach seinem Comeback in Frankfurt)