我有一个wordpress新闻门户和easyengine+wp+redis,来了几天的性能问题,我的mysql是消耗大量的cpu使用我有超过500k的帖子有人帮我解决这个问题?
打印cpuhttps://prnt.sc/jgkpwy
服务器详细信息ubuntu 16.04-最小-raid1硬盘256 gb ssd 2.5“硬盘256 gb ssd 2.5”ram 32 gb cpu intel xeon e3-1225v3
mysql配置my.cnf
# MariaDB database server configuration file.
#
# You can copy this file 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
[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
lc_messages = en_US
skip-external-locking
#
# 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
#
max_connections = 300
connect_timeout = 5
wait_timeout = 600
max_allowed_packet = 16M
thread_cache_size = 500
sort_buffer_size = 4M
bulk_insert_buffer_size = 16M
tmp_table_size = 32M
max_heap_table_size = 32M
#
# * MyISAM
#
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched. On error, make copy and try a repair.
myisam_recover_options = BACKUP
key_buffer_size = 128M
# open-files-limit = 2000
table_open_cache = 600
myisam_sort_buffer_size = 512M
concurrent_insert = 2
read_buffer_size = 2M
read_rnd_buffer_size = 1M
#
# * Query Cache Configuration
#
# Cache only tiny result sets, so we can fit more in the query cache.
query_cache_limit = 2M
query_cache_size = 256M
query_cache_strip_comments =1
# for more write intensive setups, set to DEMAND or OFF
query_cache_type = 1
#
# * 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 logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# we do want to know about network errors and such
log_warnings = 2
#
# Enable the slow query log to see queries with especially long duration
# slow_query_log[={0|1}]
slow_query_log_file = /var/log/mysql/mariadb-slow.log
long_query_time = 10
# log_slow_rate_limit = 1000
log_slow_verbosity = query_plan
# log-queries-not-using-indexes
# log_slow_admin_statements
#
# 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
# report_host = master1
# auto_increment_increment = 2
# auto_increment_offset = 1
# log_bin = /var/log/mysql/mariadb-bin
# log_bin_index = /var/log/mysql/mariadb-bin.index
# not fab for performance, but safer
# sync_binlog = 1
# expire_logs_days = 10
# max_binlog_size = 100M
# slaves
# relay_log = /var/log/mysql/relay-bin
# relay_log_index = /var/log/mysql/relay-bin.index
# relay_log_info_file = /var/log/mysql/relay-bin.info
# log_slave_updates
# read_only
#
# If applications support it, this stricter sql_mode prevents some
# mistakes like inserting invalid dates etc.
# sql_mode = NO_ENGINE_SUBSTITUTION,TRADITIONAL
#
# * 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!
default_storage_engine = InnoDB
# you can't just change log file size, requires special procedure
# innodb_log_file_size = 50M
innodb_buffer_pool_size = 15G
innodb_log_buffer_size = 16M
innodb_file_per_table = 1
innodb_open_files = 400
innodb_io_capacity = 400
innodb_flush_method = O_DIRECT
innodb_buffer_pool_instances = 15
#
# * 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
#
# * Galera-related settings
#
[galera]
# Mandatory settings
# wsrep_on=ON
# wsrep_provider=
# wsrep_cluster_address=
# binlog_format=row
# default_storage_engine=InnoDB
# innodb_autoinc_lock_mode=2
#
# Allow server to accept connections on all interfaces.
#
# bind-address=0.0.0.0
#
# Optional setting
# wsrep_slave_threads=1
# innodb_flush_log_at_trx_commit=0
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
# no-auto-rehash # faster start of mysql but no tab completion
[isamchk]
key_buffer = 16M
#
# * 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/
3条答案
按热度按时间fquxozlt1#
你提到的所有慢查询都涉及
wp_postmeta
. wp有一个非常低效的表模式。我在这里概述了几种修复方法。如果改进该模式后仍然存在问题,我们可以讨论进一步的步骤。你不能调整你的方式走出一个高cpu的问题。但是,有一个设置太高:
为了便于阅读,下面是一个缓慢的查询:
请使用
-s t
使用时mysqldump
.附录
鉴于此:
这可能会以最少的努力给您带来最大的好处:
注意:执行此操作需要一些时间
ALTER
; 这张table将被封锁。如果那样的话
ALTER
导致“重复的关键”,显然你有相同的“关键”多次为一个给定的“职位”。任何一个输入数据时出错。在这种情况下,应该清除数据。或者。。。
你有一个重复的meta\u键。在这种情况下,将pk行更改为
ADD PRIMARY KEY(post_id, meta_key, meta_id),
.dced5bon2#
我的.cnf-ini[mysqld]部分需要考虑的建议
请随时通知我们进展情况。
如果你想发布ulimit-a的文本结果并显示全局状态;显示全局变量;可以提供其他有益的建议。
ryoqjall3#
对my.cnf-ini[mysqld]部分的建议
使用set全局变量\u name=value后;为确保正确和允许的限制,请在移动到下一个变量之前运行一分钟,在下一个设置全局变量之前始终检查错误日志,以确保没有造成任何伤害,然后当您位于列表末尾时,使用成功的变量值编辑my.cnf-ini,关闭/重新启动。
uvwl可能必须保持开启是的,见refman。
我想通过skype和teamviewer观察您的测试和实施。今天,如果可能的话(早点)。
可能无法动态设置和测试的其他my.cnf-ini[mysqld]更改包括:
额外的分析将发现更多的机会。