MySQLTuner is a script written in Perl that will assist you with your MySQL configuration and make recommendations for increased performance and stability.
GNU General Public License v3.0
8.98k
stars
1.29k
forks
source link
mysqltuner recommends variable-change thats already been set #770
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[OK] InnoDB File per table is activated
[OK] InnoDB Buffer Pool size ( 6.0G ) under limit for 64 bits architecture: (17179869184.0G )
[OK] InnoDB buffer pool / data size: 6.0G / 5.4G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (16.6666666666667%): 1.0G * 1 / 6.0G should be equal to 25%
[--] Number of InnoDB Buffer Pool Chunk: 64 for 1 Buffer Pool Instance(s)
[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
[OK] InnoDB Read buffer efficiency: 99.92% (1347586855 hits / 1348643358 total)
[OK] InnoDB Write Log efficiency: 94.56% (28402487 hits / 30036436 total)
[OK] InnoDB log waits: 0.00% (0 waits / 1633949 writes)
[...]
-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
Be careful, increasing innodb_log_file_size / innodb_log_files_in_group means higher crash recovery mean time
Variables to adjust:
innodb_log_file_size should be (=1G) if possible, so InnoDB total log file size equals 25% of buffer pool size.
Setting of the DB is:
INNODB_LOG_FILE_SIZE 1073741824
there is NO 'innodb_log_files_in_group' which is used in the associated calculation in Line 6443.
MariaDB 10.11.6 MysqlTuner 2.5.2
Setting of the DB is:
there is NO 'innodb_log_files_in_group' which is used in the associated calculation in Line 6443.
maybe releated: https://github.com/major/MySQLTuner-perl/issues/565