Inside君整理了一份最新基于MySQL 5.6和5.7的配置文件模板，基本上可以說覆蓋90%的調(diào)優(yōu)選項(xiàng)，用戶只需根據(jù)自己的服務(wù)器配置稍作修改即可，如InnoDB緩沖池的大小、IO能力（innodb_buffer_pool_size，innodb_io_capacity)。特別注意，這份配置文件不用修改，可以直接運(yùn)行在MySQL 5.6和5.7的版本下，這里使用了小小的技巧，具體可看配置文件。如果配置參數(shù)存在問題，也可以及時(shí)反饋Inside君，我們一起成長(zhǎng)。
觸發(fā)Inside君做這件事情的原因是大部分網(wǎng)絡(luò)上的MySQL配置文件都非常非常古老，大多都是基于MySQL 5.1的版本，這導(dǎo)致了絕大部分MySQL并沒有運(yùn)行在最優(yōu)的環(huán)境，從而導(dǎo)致一些錯(cuò)誤的使用，亦或是災(zāi)難性事故的發(fā)生，比如數(shù)據(jù)丟失，主從數(shù)據(jù)不一致等。而這些問題早在5.6版本及以后的版本中得到了解決。
最后，拋棄你那所謂的、陳舊的、錯(cuò)誤的MySQL配置文件，面向一個(gè)嶄新的高性能、高可靠、高可擴(kuò)展MySQL時(shí)代，你要做的就是下載這份配置文件并用于你的生產(chǎn)環(huán)境。配置如下：
| [client]user=davidpassword=88888888 [mysqld]########basic settings########server-id = 11port = 3306user = mysqlbind_address = 10.166.224.32autocommit = 0character_set_server=utf8mb4skip_name_resolve = 1max_connections = 800max_connect_errors = 1000datadir = /data/mysql_datatransaction_isolation = READ-COMMITTEDexplicit_defaults_for_timestamp = 1join_buffer_size = 134217728tmp_table_size = 67108864tmpdir = /tmpmax_allowed_packet = 16777216sql_mode = "STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER"interactive_timeout = 1800wait_timeout = 1800read_buffer_size = 16777216read_rnd_buffer_size = 33554432sort_buffer_size = 33554432########log settings########log_error = error.logslow_query_log = 1slow_query_log_file = slow.loglog_queries_not_using_indexes = 1log_slow_admin_statements = 1log_slow_slave_statements = 1log_throttle_queries_not_using_indexes = 10expire_logs_days = 90long_query_time = 2min_examined_row_limit = 100########replication settings########master_info_repository = TABLErelay_log_info_repository = TABLElog_bin = bin.logsync_binlog = 1gtid_mode = onenforce_gtid_consistency = 1log_slave_updatesbinlog_format = rowrelay_log = relay.logrelay_log_recovery = 1binlog_gtid_simple_recovery = 1slave_skip_errors = ddl_exist_errors########innodb settings########innodb_page_size = 8192innodb_buffer_pool_size = 6Ginnodb_buffer_pool_instances = 8innodb_buffer_pool_load_at_startup = 1innodb_buffer_pool_dump_at_shutdown = 1innodb_lru_scan_depth = 2000innodb_lock_wait_timeout = 5innodb_io_capacity = 4000innodb_io_capacity_max = 8000innodb_flush_method = O_DIRECTinnodb_file_format = Barracudainnodb_file_format_max = Barracudainnodb_log_group_home_dir = /redolog/innodb_undo_directory = /undolog/innodb_undo_logs = 128innodb_undo_tablespaces = 3innodb_flush_neighbors = 1innodb_log_file_size = 4Ginnodb_log_buffer_size = 16777216innodb_purge_threads = 4innodb_large_prefix = 1innodb_thread_concurrency = 64innodb_print_all_deadlocks = 1innodb_strict_mode = 1innodb_sort_buffer_size = 67108864########semi sync replication settings########plugin_dir=/usr/local/mysql/lib/pluginplugin_load = "rpl_semi_sync_master=semisync_master.so;rpl_semi_sync_slave=semisync_slave.so"loose_rpl_semi_sync_master_enabled = 1loose_rpl_semi_sync_slave_enabled = 1loose_rpl_semi_sync_master_timeout = 5000 [mysqld-5.7]innodb_buffer_pool_dump_pct = 40innodb_page_cleaners = 4innodb_undo_log_truncate = 1innodb_max_undo_log_size = 2Ginnodb_purge_rseg_truncate_frequency = 128binlog_gtid_simple_recovery=1log_timestamps=systemtransaction_write_set_extraction=MURMUR32show_compatibility_56=on |
