mysql之my.cnf

最新推荐文章于 2024-05-27 15:06:29 发布

沉默王二

最新推荐文章于 2024-05-27 15:06:29 发布

阅读量6.6k

点赞数 3

文章标签： mysql my-cnf 性能

本文链接：https://blog.csdn.net/qing_gee/article/details/49507817

版权

mysql在安装完毕后，一般都要对my.cnf进行配置，以期mysql性能最大化。

一、关键参数

此配置是通过我们的大宗期货交易平台性能整理出来，希望你只是做一个参照。

[client]
#no-beep
port=3306

[mysql]
default-character-set=utf8
socket          = /var/lib/mysql/mysql.sock

[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
socket          = /var/lib/mysql/mysql.sock

character-set-server=utf8

#默认引擎设置为INNODB，这要看你的数据库是做什么用的
default-storage-engine=INNODB
#最大连接数，这个说实话，我没有测出来最合理的数值
max_connections = 500
#下面这两个参数就是禁用缓存查询，主要是因为我的数据库大量的写操作，所以设置了cache，反而会影响性能，也是基于理论上的，所以你大可不必相信。
query_cache_size=0
query_cache_type=0

#这几个数值，你千万要找度娘理论一下啊，我是说不清楚了
table_open_cache=2000
tmp_table_size=19M
thread_cache_size = 18
myisam_max_sort_file_size = 1G
myisam_sort_buffer_size=30M
key_buffer_size=8M
read_buffer_size = 512K
read_rnd_buffer_size = 1M
sort_buffer_size = 512k

#这个很重要了，对性能有着很大的影响，我会告诉你的。
innodb_flush_log_at_trx_commit=2

innodb_log_buffer_size=1M

# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
innodb_buffer_pool_size=2G
innodb_buffer_pool_instances=1
#上面这两个参数对性能的作用我会论证给你的。

#这一块参数的作用我也忘的差不多了，所以度娘吧
innodb_log_file_size=48M
innodb_thread_concurrency=9
innodb_autoextend_increment=64
innodb_buffer_pool_instances=8
innodb_concurrency_tickets=5000
innodb_old_blocks_time=1000
innodb_open_files=300
innodb_stats_on_metadata=0
innodb_file_per_table=1
innodb_checksum_algorithm=0
flush_time=0
join_buffer_size=256K
max_connect_errors=100
max_allowed_packet = 16M
open_files_limit=4161
table_definition_cache=1400
binlog_row_event_max_size=8K

#二进制的类型，这个有很大学问，稍候我也会告诉你的。
binlog-format = MIXED

#事务锁时间，这个同样学问很大。
innodb_lock_wait_timeout = 20

#事务锁级别，这个学问同样很大很大啊
transaction-isolation = REPEATABLE-READ


binlog_cache_size = 1M

# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
#这个参数就是设置二进制文件的路径的，注意啊，注意啊！
log_bin=mysql-bin

server_id = 1

[mysqldump]
max_allowed_packet = 16M

二、innodb_flush_log_at_trx_commit

Controls the balance between strict ACID compliance for commit operations, and higher performance
that is possible when commit-related I/O operations are rearranged and done in batches. You can
achieve better performance by changing the default value, but then you can lose up to a second of
transactions in a crash.
• The default value of 1 is required for full ACID compliance. With this value, the contents of the InnoDB
log buffer are written out to the log file at each transaction commit and the log file is flushed to disk.
• With a value of 0, the contents of the InnoDB log buffer are written to the log file approximately once
per second and the log file is flushed to disk. No writes from the log buffer to the log file are performed
at transaction commit. Once-per-second flushing is not 100% guaranteed to happen every second,
due to process scheduling issues. Because the flush to disk operation only occurs approximately once
per second, you can lose up to a second of transactions with any mysqld process crash.
• With a value of 2, the contents of the InnoDB log buffer are written to the log file after each transaction
commit and the log file is flushed to disk approximately once per second. Once-per-second flushing
is not 100% guaranteed to happen every second, due to process scheduling issues. Because the
flush to disk operation only occurs approximately once per second.

innodb_flush_log_at_trx_commit=1，innodb的缓存会在事务提交或者每秒钟时都会进行磁盘的刷新操作，默认值。
innodb_flush_log_at_trx_commit=2，innodb缓存会在提交事务时写入到事务日志但不会刷新磁盘，然后在每秒钟时进行磁盘刷新操作。
innodb_flush_log_at_trx_commit=0，每秒钟时缓存写入日志，同时刷新磁盘。

根据我们的性能测试，发现在innodb_flush_log_at_trx_commit=2，数据的读写速度和1的时候有明显的提升。

三、innodb_buffer_pool_size、innodb_buffer_pool_instances

这两个参数，你必须得看看这个mysql：提升性能的最关键参数

四、binlog-format = MIXED

该种二进制日志模式是statement和row模式的结合体，不过需要注意的是mysql 5.7中的默认格式是STATEMENT，这会影响到服务端代码如java对事务的处理，非常关键，没有调试好的话，会导致事务不回滚。

In MySQL 5.7, the default format is STATEMENT.
You must have the SUPER privilege to set either the global or session binlog_format value.
The rules governing when changes to this variable take effect and how long the effect lasts are the same as for other MySQL server system variables. See Section 13.7.4, “SET Syntax”, for more information.
When MIXED is specified, statement-based replication is used, except for cases where only row-based replication is guaranteed to lead to proper results. For example, this happens when statements contain user-defined functions (UDF) or the UUID() function. An exception to this rule is that MIXED always uses statement-based replication for stored functions and triggers.