Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi,
The MySQL processes in that list are actually different threads. In htop’s settings, you can configure it to not show separate threads for each process which can make it much simpler and more useful to look at. So, what you’re seeing there is really MySQL using 10.4% of your server’s memory.
As memory is increasing when you have many concurrent requests, the memory increase is likely due to the additional PHP processes that are needed to handle the requests. When a request comes in but there are no available PHP worker processes for the app (that is, they are all busy handling a request), PHP-FPM will create an additional process for the new request. If your request concurrency later goes down, after a period of time PHP-FPM will kill any PHP processes that have been idle (not needed to handle requests) and memory usage will go down.
For more information on memory usage on ServerPilot and ways to reduce memory usage, see here:
https://serverpilot.io/community/articles/how-to-reduce-php-and-wordpress-memory-usage.html
I’m glad the htop suggestion helped. That’s the first thing I change in htop on any new server of my own.
Regarding the memory usage remaining high, I suggest opening a support ticket with ServerPilot. There’s almost certainly a good explanation for what you’re seeing but it will take more information and possibly us looking directly at your server to determine it.