• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Question Memory usage after backup

Unfortunately this leads me nicely back in the same circle again
We have not been able to identify anything unusual about the clients website setup that would cause high usage of phpfpm that could be classed as excessive.

Mysql continues to clime continually throughout the day.
The phpfpm is stable and consistent - It is the mysql memory and mariadb memory that is filling uncontrollably.

The only correlation is that process manager is reporting 100% ram usage at the moments leading to mariadb being killed - mariadb is occupying approx 90% of it and system the 0ther 10% inclusive of cache values.

It shouldnt kill mariadb - mariadb shouldnt be occupying the entire ram?
 
The journal file looks like this:
...
Aug 21 09:44:41 servername.ipaddress.plesk.page systemd[1]: mariadb.service: Consumed 10h 5min 17.784s CPU time, 20.0G memory peak, 7.4G memory swap peak.
...
20 GB + 7.4 GB = 27.4 GB.
Your total RAM: 40 GB

The RAM manager does not kill MariaDB, because MariaDB occupies all RAM. It kills MariaDB as one out of several measures, because the total RAM usage exceeds a limit. MariaDB is not your problem.

But I've written it now several times, pointing out that neither the monitoring charts, nor the journalctl log shows that MariaDB is a problem. Instead, the monitoring shows that Apache and PHP are causing the problem. So in some ways, yes, you're running in circles. To me the situation is clear, but there is nothing I can do here if you believe the problem lies in MariaDB.
 
Thanks Bitpalast I appreciate your input on this.
I can see you have repeatedly stated you think it is PHP. Im repeatedly saying I dont think it is PHP because if this were the case why would running a backup cause an increase in memory consulption and not release it? Doesnt sound like that could be PHP related?

Even if a query is intensive when it finishes it shouldnt cause the memory to stay allocated?

Im still investigating this at the moment.
 
Back
Top