I'm assuming Cpanel doesn't dynamically adjust the my.cnf file by examining the total RAM for your system and therefore it comes set to be very conservative on memory use so systems with a small amount of RAM don't have issues.
I played around with MySQLTuner and theot her popular tool, Tuning Primer. More recent reports seem to indicate Tuning Primer is the better tool but MySQLTuner is popular because it's been around longer.
In 4 days I got 3 notifications mysqld had stopped responding and needed to be restarted. In addition WHM has its own optimization recommendations.
The main conflict between WHM's recommendation and these tools is WHM keeps recommending innodb_buffer_pool_size = 128M where the others want me to set it to around at least half the total memory size of 4G!
There's a gazillion settings you can change. My 8GB system is way underutilized. It has maybe 20 users on the main app that uses the DB, and the stats were showing on average 5-8 simultaneous active DB connections at any given time.
There are quite a few tables with a decent amount of data. About 150 tables, most very small but a couple large ones, the largest being over 50 fields, with 10K records taking 10MB of storage. The entire DB is 2GB in size.
I'm wondering if there is a setting or a different tool other than WHM and the other two I mentioned that really just gives you some primary conservative config change recommendations or is MySQLTuner or TuningPrimary reliable and conservative enough to follow all the recommendations safely?
I'm not having performance issues but when you have got nearly 6GB free memory on an 8GB system I might as well let MariaDB take advantage of some of that free memory to cache more data!
Please sign in to leave a comment.