MySql overload using all memory on the droplet

  • Posted on July 2, 2013
  • leoAsked by leo


Im migrated a buddypress site to a droplet with 512mb . and im having some issues.

The first instalation was fine but when i did the dump / export tables from wordpress, the mysql started to crash.

Then i created the swap and it stopped to crash BUT still couldnt use the server.

Then i did the changes on my.cnf and apache.conf ( and i can use it for 1 minute than it overload again but didnt crash

This is my free -m total used free shared buffers cached Mem: 491 482 8 0 1 17 -/+ buffers/cache: 464 26 Swap: 511 506 5

The database only have 8mb… its not possible to be eating all the free memory…

Submit an answer

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!

Sign In or Sign Up to Answer

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.


What you can also do is to use the MySQLTuner script.

The MySQLTuner is a script written in Perl and allows you to quickly test your MySQL configuration and it gives you suggestions for adjustments to increase performance and stability.

According to the official GitHub page, it supports 300 indicators for MySQL/MariaDB/Percona Server in this last version.

To run the script you could do the following:

  • SSH to your Droplet
  • Download the script:
wget -O
  • Then execute it:

The script would run multiple checks against your MySQL instance, all checks done by MySQLTuner are documented here.

Also as stated in the official documentation, it is still extremely important for you to fully understand each change you make to a MySQL database server. If you don’t understand portions of the script’s output, or if you don’t understand the recommendations, you should consult a knowledgeable DBA or system administrator that you trust.

As a good practice make sure to always test your changes on staging environments before implementing them on your production database.

On the same note, if you want to have a worry-free MySQL hosting and focus on your application, I would recommend trying out the DigitalOcean Managed Databases:

This was mini tutorial was posted from bobbyiliev in this question in our community:

Hope that this helps! Regards, Alex

installed memcache and xcache… oh boy… huge difference !

There’s actually 856MB used, the rest are cached. The memory usage looks fine - you shouldn’t experience any more crashes.