• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Apache consuming RAM and not releasing until traffic slows down

Bart Marek

New Pleskian
1vnr2

Just wondering is someone seen situation like that. When the server hits high number of visitors Apache starts to consume RAM and not release it. So in a few hours it consumes all available RAM. I have absorved it for few years now, and just wonder if PLESK just can not handle that much traffic or it is just miss-configuration of the Apache. I'm attaching screenshots of that incident.
JustPaste.it - Share Text & Images the Easy Way
 
It should not be a big problem as part of the RAM might not be "in use" and could be requested by other applications. What you should do in such a situation is to look into the process list, e.g. on Debian
# ps aux | grep apache2
or on RHEL/Centos
# ps aux | grep httpd
and check the real RAM usage of the processes there. It should not be very high. If it is, you could use
# strace -p <pid>
with "<pid>" being the process ID of the Apache process that is using much RAM, to see what that process is currently doing. That way you can trace the reason to the cause and resolve the cause.
 
Thanks for your response Peter. It is a big problem, because it does actually holds that memory, bottom part of the attached screenshot shows TOP command showing those 3.8GB files that PHP-PFM files. This year I gave server 64GB of ram and we only got to 30GB so we were fine this year, but last year we had 16GB of RAM and apache eat all of it, once that happened website was still fine since Apache and mySQL had the RAM but everything else was stuck, you could not even run LS command due to lock of memory.
 
I understand that this is a big problem when system resources run short, but what have you found out using the methods I described, especially strace?
 
Sorry Peter. We only have that problem once a year day before Thanksgiving since we sell smoked turkeys. I'll let you know next year. I was just looking for someone who faced that problem as well, just more often than I.
 
In this case it is quite obvious that the load that your website generates is simply too high. You'll need to check your scripts thoroughly and speed them up.
 
In that case I'll stick with adding more RAM, nowadays thanks to companies like DigitalOcean, you can for $40 buy 128GB of ram for a week, and then go down to 4GB for the rest of the year. Have a great day.
 
Back
Top