Changes

One thing you should look at is the query cache. By default, the query cache is turned off. You should turn it on, and set it in the tens of megabytes to see how it affects performance (like 80MB for starters). A huge cache will hurt performance (don't give it 4GB just because you have 32GB of RAM). But some amount of cache will definitely improve performance. So you just have to find the sweetspot for your hardware and application. That being said, if your tables are exclusively InnoDB tables, then you might be able to turn query cache off. <ref>Hayden James: https://haydenjames.io/mysql-query-cache-size-performance/</ref> <ref>https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html</ref> <ref>https://dba.stackexchange.com/questions/167271/mariadb-mysql-tuner-report-confusing</ref> <ref>https://dba.stackexchange.com/questions/66774/why-query-cache-type-is-disabled-by-default-start-from-mysql-5-6/66796#66796</ref>

The best tuning parameters are <ref>Bill Karwin, Percona http://www.slideshare.net/billkarwin/mysql-55-guide-to-innodb-status</ref> <ol># <li><code>innodb_buffer_pool_size</code> as much as you can spare after OS and MySQL# <code>innodb_log_file_size</code> at least enough for 60 minutes A rule of log writes (because sequential writes thumb would be to make it 10% larger than your database size. If it's 10% smaller than your db, you probably won't notice a log file are faster than disk)# <code>innodb_io_capacity</code> based problem. This is one reason to run your DB on your disk IOPSa dedicated server: so that you can allocate as much memory as possible to the database without worrying about other OS and application memory requirements.<ref>Bill Karwin, Percona httphttps://www.slidesharepercona.netcom/blog/2011/04/billkarwin04/mysqlinnodb-55flushing-guidetheory-toand-innodb-statussolutions/</ref> <ref>https://www.percona.com/blog/20082007/11/2103/howchoosing-to-calculate-a-good-innodb-log-file-sizeinnodb_buffer_pool_size/</ref> <ref> See [https://wwwdev.perconamysql.com/blogdoc/2011refman/045.7/04en/innodb-flushingbuffer-theorypool-and-solutions/resize.html the manual] for resizing the buffer.<li><code>innodb_log_file_size</refcode>at least enough for 60 minutes of log writes (because sequential writes to a log file are faster than disk) <ref>https://www.percona.com/blog/20072008/11/0321/choosinghow-to-calculate-a-good-innodb-log-file-innodb_buffer_pool_sizesize/</ref>Do this at peak usage, or use a bigger time window for sampling.<source lang="bashmysql">SHOW ENGINE INNODB STATUS-- turn on the pager; setting it to 'grep sequence'pager grep sequence-- run our status report; wait 60 seconds and run it againshow engine innodb status\Gselect sleep(60); show engine innodb status\G-- turn the pager offnopager</source>Now you take the last number minus the first number, and convert to MB<source lang="mysql">select (43599802491 - 43599758916) / 1024 / 1024 as MB_per_minute;