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 @danielpcharrua,
I’ll recommend using the top or htop command. These commands will show you the top commands using CPU,RAM, time it has been running etc.
It’s possible the problem is related to a lot of traffic or the websites/applications are too heavy which generates the RAM being eaten. You’ll be able to confirm this with the above commands. Additionally, you can use the ps aux command to see all the processes and see which one you would need to either kill or further investigate why it’s taking so much memory.
Additionally, check if you haven’t actually configured any cron jobs which spawn and create traffic. The cron jobs might be generating MySQL queries which does tend to take a lot of Memory if they are being executed for more than 60 seconds.
It’s good to enable slow query log for MySQL to see if there are any slow queries. If there are, I’ll recommend working towards optimizing your queries.
Lastly, I believe it will be best to test this as soon as you receive an e-mail about high load.
Regards, KDSys
It doesn’t look like an overwhelming number of HTTP processes running, but check your access_log for lots of requests to XML-RPC. That seems to be a favorite attack point and enough requests can easily overwhelm a droplet. I would also check your security log, /var/log/secure on centos, for ssh login attempts. I recently had a server overwhelmed by login attempts and had to put a more aggressive fail2ban policy in place.