gpt4 book ai didi

mysql - 非常慢的mysql

转载 作者:行者123 更新时间:2023-12-01 00:16:14 25 4
gpt4 key购买 nike

我的服务器 mysql 有一个大问题。一切正常,但自一周以来,速度非常慢。每个查询都很慢(有时超过 20 秒)。我的配置中没有任何更改。

有人可以帮助我知道为什么我的服务器现在很慢吗?

谢谢。

这是我的 my.cnf:

[

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
language = /usr/share/mysql/english
#join_buffer_size = 128.0K
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
#
key_buffer = 16M
max_allowed_packet = 16M
max_heap_table_size = 64M
tmp_table_size = 64M

thread_stack = 128K
thread_cache_size = 8
#max_connections = 100
table_cache = 400
join_buffer_size = 2000K
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# 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.
#server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * 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!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
innodb_buffer_pool_size = 42M
#
# * 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 = 16M

最佳答案

假设资源方面(cpu、内存、磁盘事件)没有发生任何变化——要研究的一个领域可能是查询的索引。假设数据不断被输入/更新,那么随着越来越多的数据被输入,查询可能会随着时间的推移而变慢——尤其是在没有设置索引的情况下。如果没有关于您的整个设置的更多信息,这种问题很难回答。

关于mysql - 非常慢的mysql,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/1786658/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com