Hello, all
What you can also do is to use the MySQLTuner script. in order to make sure that your MySQL config is using the recommended values against the available resources on your server.
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 http://mysqltuner.pl/ -O mysqltuner.pl
perl mysqltuner.pl
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:
https://www.digitalocean.com/products/managed-databases-mysql/
This was mini tutorial was posted from bobbyiliev in this question in our community: https://www.digitalocean.com/community/questions/how-to-tweak-mysql-mariadb-configuration-for-increased-performance-and-stability
Hope that this helps!
Regards,
Alex
Is mysqld running out of memory?
You might be getting hit with XML-RPC attacks (seems to be a popular thing these days), which cause the out-of-memory condition.
See these two links:
https://www.digitalocean.com/community/questions/error-establishing-a-database-connection-wordpress
https://www.digitalocean.com/community/tutorials/how-to-protect-wordpress-from-xml-rpc-attacks-on-ubuntu-14-04
Yes I am having many of these XML-RPC attacks and decided to implement the changes to the vi /etc/nginx/sites-available/wordpress conf.
How can I verify that it works?
Can my server still be underdimensioned because of these attacks?
check for the return code in your access log file. it should change to 500 instead of 200