Hello everyone,
on peak hours we are experiencing a severe high RAM usage that bring our server to a total hang, such that we are forced to reboot it.
Server environment
Server: Virtual machine based on OnApp / Xen technology
RAM: 6GB
OS: Cloudlinux 5.8 x86_64
Panel: Cpanel /WHM 11.32.3 (build 21)
Total accounts: ~125 accounts.
Services: websites (all sites are made by us for our clients) + mail services, etc.
What we tried to do until now (also with the help of an expert server admin)
I expected that Cloudlinux (even with default settings: 25% CPU, 20 Max processes and memory limits disabled) would have been able to prevent the server from crashing due to a single "heavy" account.
Any ideas?
on peak hours we are experiencing a severe high RAM usage that bring our server to a total hang, such that we are forced to reboot it.
Server environment
Server: Virtual machine based on OnApp / Xen technology
RAM: 6GB
OS: Cloudlinux 5.8 x86_64
Panel: Cpanel /WHM 11.32.3 (build 21)
Total accounts: ~125 accounts.
Services: websites (all sites are made by us for our clients) + mail services, etc.
What we tried to do until now (also with the help of an expert server admin)
- We added 2GB of RAM (from 4GB to 6GB)
- Installed the Cloudlinux environment (at the moment we kept the memory limit disabled as default)
- Installed the mysql db governor tool provided by Cloudlinux
- Installed nginx (but then we reverted to Apache, since it didn't help).
- Switched from SuPHP to FastCGI
- Tuned many MySQL settings in my.cnf in order to improve performance. We also used the mysqltuner to analyze and config MySQL server.
- On the most busy websites we installed cache plugins in order to reduce the time spent on PHP execution.
- We forced websites not to use mysql persistent connections.
- We distribute cron jobs over time so that they overlap as few as possible.
- In the end we suspended the most single heavy website to reduce load, and it looks this is the only way we found to prevent the server from crashing again.
I expected that Cloudlinux (even with default settings: 25% CPU, 20 Max processes and memory limits disabled) would have been able to prevent the server from crashing due to a single "heavy" account.
Any ideas?