• 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 High apache usage

5 GB for Apache does not sound very much to me. The RAM that the process uses depends on the RAM that scripts that are run by that process occupy. It depends, too, on the number of Apache modules that are activated and the number of Apache instances. However, there is not much CPU load, so maybe there really is no problem, just ordinary usage by scripts?
 
Questions:
  • You have mod_pagespeed turned on and maybe by mistake added a huge Cache?
  • php with too large memory opcache?
  • ...
Apart from that there is still a possiblity of a lot of open connections or plain an attack. Somethign like a SYN-flood variant etc. So: check process listo on how many Apache processes are running and how much open connections you have.
 
+1... same problem.
From December I've Apache memory high usage, despite low server workload.
To reset I need every time to create a hosting/subdomain and delete it (and the apache memory restart from 10%... but after 2/3 days it returns to 50/60%).
I think the problem is with PHP but I don't know how to fix it.
 
60% memory usage means that you have 40% left. What exactly makes you worry? Did you experience outages due to exhausted RAM on the affected system?
 
After 5/7 days is 100% (every 3/4 days I reset the apache memory activating/deleting a subdomain).
The problem appeared only from December, without any significant change in the server configuration.
Before of December the Apache memory was always 20/30% maximum.
 
Yes, you're right!
I've changed from "static" (I don't know because a lot of hosting had this value set) to "on demand" and now the apache memory behaviour is returned normal.
Thanks!
 
Back
Top