2017-02-24 58 views
0

當前有一個MySQL數據庫,並且遇到MySQL在600%的CPU使用率下運行的問題。MySQL CPU Maxing

規格:

2.3 GHz英特爾至強E5-2686 V4(Broadwell微架構)處理器或2.4 GHz英特爾至強E5-2676 V3(Haswell的)處理器

8個vCPU的

32GB的RAM

100GB硬盤。

實例當前由AWS託管,運行Ubuntu 14.04.4 LTS和MySQL版本5.6.33-0ubuntu0.14.04.1-log。

請參閱my.cnf配置如下:

# The MySQL database server configuration file. 

# You can copy this to one of: 
# - "/etc/mysql/my.cnf" to set global options, 
# - "~/.my.cnf" to set user-specific options. 
# 
# One can use all long options that the program supports. 
# Run program with --help to get a list of available options and with 
# --print-defaults to see which it would actually understand and use. 
# 
# For explanations see 
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html 

# This will be passed to all mysql clients 
# It has been reported that passwords should be enclosed with ticks/quotes 
# escpecially if they contain "#" chars... 
# Remember to edit /etc/mysql/debian.cnf when changing the socket location. 
[client] 
port  = 3306 
socket  = /var/run/mysqld/mysqld.sock 

# Here is entries for some specific programs 
# The following values assume you have at least 32M ram 

# This was formally known as [safe_mysqld]. Both versions are currently parsed. 
[mysqld_safe] 
socket  = /var/run/mysqld/mysqld.sock 
nice  = 0 
log_error=/var/log/mysql/mysql_error.log 

[mysqld] 
# 
# * Basic Settings 
# 
user  = mysql 
pid-file = /var/run/mysqld/mysqld.pid 
socket  = /var/run/mysqld/mysqld.sock 
port  = 3306 
basedir  = /usr 
datadir  = /var/lib/mysql 
tmpdir  = /tmp 
lc-messages-dir = /usr/share/mysql 
skip-external-locking 

innodb_io_capacity = 2000 
innodb_read_io_threads = 64 
innodb_thread_concurrency = 0 
innodb_write_io_threads = 64 
innodb_buffer_pool_size = 2G 
innodb_log_file_size = 1G 

# Skip reverse DNS lookup of clients 
skip-name-resolve 

# 
# Instead of skip-networking the default is now to listen only on 
# localhost which is more compatible and is not less secure. 
bind-address  = 127.0.0.1 
# 
# * Fine Tuning 
# 
key_buffer  = 11G 
max_allowed_packet = 16M 
thread_stack  = 192K 
thread_cache_size  = 8 
# This replaces the startup script and checks MyISAM tables if needed 
# the first time they are touched 
myisam-recover   = BACKUP 
#max_connections  = 100 
#table_cache   = 64 
#thread_concurrency  = 10 
# 
# * Query Cache Configuration 
# 
query_cache_limit = 1M 
query_cache_size  = 16M 
query_cache_type = 0 
# 
# * Logging and Replication 
# 
# Both location gets rotated by the cronjob. 
# Be aware that this log type is a performance killer. 
# As of 5.1 you can enable the log at runtime! 
general_log_file  = /var/log/mysql/mysql.log 
general_log    = 1 
# 
# Error log - should be very few entries. 
# 
log_error = /var/log/mysql/mysql_error.log 
# 
# Here you can see queries with especially long duration 
#log_slow_queries = /var/log/mysql/mysql-slow.log 
#long_query_time = 2 
#log-queries-not-using-indexes 
# 
# The following can be used as easy to replay backup logs or for replication. 
# note: if you are setting up a replication slave, see README.Debian about 
#  other settings you may need to change. 
#server-id  = 1 
#log_bin   = /var/log/mysql/mysql-bin.log 
expire_logs_days = 10 
max_binlog_size   = 100M 
#binlog_do_db  = include_database_name 
#binlog_ignore_db = include_database_name 
# 
# * InnoDB 
# 
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. 
# Read the manual for more InnoDB related options. There are many! 
# 
# * Security Features 
# 
# Read the manual, too, if you want chroot! 
# chroot = /var/lib/mysql/ 
# 
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca". 
# 
# ssl-ca=/etc/mysql/cacert.pem 
# ssl-cert=/etc/mysql/server-cert.pem 
# ssl-key=/etc/mysql/server-key.pem 

[mysqldump] 
quick 
quote-names 
max_allowed_packet = 16M 

[mysql] 
#no-auto-rehash # faster start of mysql but no tab completition 

[isamchk] 
key_buffer  = 512M 

# 
# * IMPORTANT: Additional settings that can override those from this file! 
# The files must end with '.cnf', otherwise they'll be ignored. 
# 
!includedir /etc/mysql/conf.d/ 
+0

儘管我無法確定它看起來像是對標準配置進行了一些更改。如果是這樣,他們通常需要「協調一致」,這意味着您要相應地遵循指示,同時考慮到您系統的資源。並不是說這個系統看起來就像它的短小。性能相關日誌暗示什麼? – B98

回答

0

首先,通過禁用general_log,沒有必要有它使所有的時間開始。通用日誌對於故障排除和/或測試目的非常有用,但它是生產數據庫上的性能查詢殺手。另外,如果你正在使用混合引擎(MyISAM和InnoDB),你可以給innodb_buffer_pool_size更多的內存。但是如果你只使用Innodb,你可以設置這個變量爲24G,key_buffer_size爲幾百兆字節。

如果您僅使用MyIsam,請完全禁用Innodb引擎(skip-innodb)並增加Myisam memroy相關參數,如key_buffer_size。

希望它有幫助。