-2

I've a dedicated problem..

When I make a load test with ~500 connections, CPU stay low (about 30%) but memory grow up fast ! And I have a 100% used RAM and 50% used SWAP..

An other dedicated with 2x lower configuration run easy 500 COs..

I don't know what I need to do..

Thanks for your help

2
  • 2
    What kind of services are you running on these servers? Aug 19 '14 at 23:12
  • Only Apache, MySQL, PHP
    – user238258
    Aug 20 '14 at 9:15
0

When a default install LAMP server has a problem with memory consumption, it's usually Apache.

Since mod_php is not thread safe, Apache is generally running with MPM prefork. That means that for each request server is spawning separate process. Since apache process with mod_php is usually consuming around ~35-50MB, that means that as the number of users grows so does the memory consumption.

Another problem is that apache doesn't do garbage cleanup so, process size tends to grow over time, so it's not unusual to see apache processes of size greater than 100MB.

First thing you need to do is try to tune Apache/PHP to lower your memory footprint.

Ideally, you would want to turn off all the unnecessary modules, both PHP and apache. This is some minimum set of apache modules that you will probably need:

# apachectl -t -D DUMP_MODULES
Loaded Modules:
 core_module (static)
 mpm_prefork_module (static)
 http_module (static)
 so_module (static)
 alias_module (shared)
 auth_basic_module (shared)
 authn_alias_module (shared)
 authn_file_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 deflate_module (shared)
 dir_module (shared)
 expires_module (shared)
 headers_module (shared)
 log_config_module (shared)
 mime_module (shared)
 php5_module (shared)
 rewrite_module (shared)
 setenvif_module (shared)
Syntax OK

If your users keep the connection open after the data is fetch, that means higher RAM usage for you. To circumvent that, change your Keepalive settings. You can either turn it off:

KeepAlive Off

or set really low timeout:

KeepAliveTimeout 2

Next thing is to tune prefork. Take special care in determining your MaxClient setting - this depends solely on amount of RAM you have dedicated to your Apache. Also, lower MaxRequestsPerChild to force Apache to recycle processes more often, thus avoid growth of memory usage per process:

<IfModule prefork.c>
StartServers         10
MinSpareServers      10
MaxSpareServers      30
ServerLimit          100
MaxClients           100
MaxRequestsPerChild  200
</IfModule>

You can find scripts online that calculate memory usage of Apache processes and can calculate what is the setting you can safely use for MaxClients/ServerLimit.

Moving to MySQL - it's usage isn't so depended on number of users, but still you want to tune it. The simplest way is to use mysqltuner script, but avoid listening to all advices, like increasing Query Cache. Query Cache of around 32 to 64MB is more then enough.

Hope this helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.