每12-18小時MySQL 100％CPU

Question

我繼承了Windows Server（2016），並且擁有一個不是我編寫的使用MySQL數據庫的專有軟件。 我是SQL的新手。

有客戶端軟件將全天隨機連接到服務器。 根據我們的忙碌程度，全天10到200台不同的計算機將登錄到該服務器。

我們使用帶有4個虛擬內核，8GB RAM和204GB本地磁盤的VPS。

似乎每隔12-18小時我們就會遇到軟件掛起的問題，然后任務管理器會顯示mysqld的99-100％CPU使用率

在我強制退出軟件然后重新啟動mysql服務之前，它不會再次正常運行。

這是我之前跟蹤的設置文件。

my.ini設置：

[client]
port=3306
[mysql]
no-beep=
default-character-set=utf8
[mysqld]
port=3306
datadir=C:/ProgramData/MySQL/MySQL Server 5.7\Data
character-set-server=utf8
default-storage-engine=INNODB
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
log-output=FILE
general-log=0
general_log_file="xyz.log"
slow-query-log=1
slow_query_log_file="xyz-slow.log"
long_query_time=10
log-error="xyz.err"
server-id=1
secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"
max_connections=151
table_open_cache=2000
tmp_table_size=249M
thread_cache_size=10
myisam_max_sort_file_size=100G
myisam_sort_buffer_size=486M
key_buffer_size=8M
read_buffer_size=64K
read_rnd_buffer_size=256K
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=8M
innodb_log_file_size=48M
innodb_thread_concurrency=13
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
back_log=80
flush_time=0
join_buffer_size=256K
max_allowed_packet=4M
max_connect_errors=100
open_files_limit=4161
sort_buffer_size=256K
table_definition_cache=1400
binlog_row_event_max_size=8K
sync_master_info=10000
sync_relay_log=10000
sync_relay_log_info=10000

這是用於Windows的MySQLTuner的圖片，其結果是： mysql_tuner

只是想了解我們可以在此處做什么以緩解此問題。 看來我們需要運行OPTIMIZE來修復表的碎片。

它還顯示了具有0％緩存的23M選擇。

innodb數據大小/緩沖池為687M / 8M

任何幫助，將不勝感激。

[編輯]

我只是運行了在另一個線程中找到的以下命令：

SELECT CEILING(Total_InnoDB_Bytes*1.6/POWER(1024,3)) RIBPS FROM
(SELECT SUM(data_length+index_length) Total_InnoDB_Bytes
FROM information_schema.tables WHERE engine='InnoDB') A;

我的返回值為2，所以我應該設置innodb_buffer_pool_size=2G嗎？

SET GLOBAL innodb_buffer_pool_size=2*1024*1024*1024;
會沒事的。 您有8GB的計算機。 我將花一些時間讓MySQL動態地實現此目的。 在30分鍾內使用SELECT @@innodb_buffer_pool_size; 查看它是否完成了您的動態請求。

這是SHOW CREATE TABLE的配方：

mysql> USE xyz; SHOW CREATE TABLE recipes;
Database changed
+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table   | Create Table                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| recipes | CREATE TABLE `recipes` (
  `id` int(11) NOT NULL,
  `name` varchar(64) NOT NULL,
  `dname` varchar(64) NOT NULL DEFAULT '',
  `descrpara` text NOT NULL,
  `category` varchar(32) NOT NULL,
  `costperserving` float NOT NULL DEFAULT '0',
  `batchsize` int(11) NOT NULL DEFAULT '1',
  `servname` varchar(32) NOT NULL DEFAULT 'Serving',
  `rectype` tinyint(4) NOT NULL DEFAULT '0',
  `servweight` float NOT NULL DEFAULT '0',
  `servflvol` float NOT NULL DEFAULT '0',
  `flags` tinyint(4) NOT NULL DEFAULT '0',
  `isapproved` tinyint(4) NOT NULL DEFAULT '0',
  `isapproved2` tinyint(4) NOT NULL DEFAULT '0',
  `tags` varchar(128) NOT NULL DEFAULT '',
  `allrestr` tinyint(4) NOT NULL DEFAULT '0',
  `numsides` tinyint(4) NOT NULL DEFAULT '0',
  `utensils` varchar(64) NOT NULL DEFAULT '',
  `active` tinyint(4) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

再次，我是超級新手，但是my.ini文件中是否可能顯示utf8的默認字符集，但是在此顯示了latin1？

我會在24小時后再次更新

的PasteBin鏈接

顯示全球狀態

顯示全球變量

顯示引擎的INNODB狀態

---

超過1天的正常運行時間后，MySQLTuner。 這也是在將innodb_buffer_pool_size = 8M更改為1G之后。 從那以后，mysqld的總RAM使用量約為1.25G。

MySQL Tuner 0.8.3 - Peter Chapman <peter@conglomo.co.nz>
Performing tests on localhost:3306 at Friday, 16 November 2018 6:13:41 AM
Currently running supported MySQL version 5.7.24-log
Archive Engine Installed
Berkeley DB Engine Not Installed
Federated Engine Not Installed
InnoDB Engine Installed
ISAM Engine Not Installed
NDBCLUSTER Engine Not Installed
Data in InnoDB tables: 687M (Tables: 257)
Data in MyISAM tables: 6M (Tables: 32)
Total fragmented tables: 67
All database users have passwords assigned
Up for: 1d 10h 33m 15s (49M q [397.000 qps], 38K conn, TX: 43G, RX: 3G)
Reads / Writes: 99% / 1%
Total buffers: 1.0G global + 1.1M per thread (151 max threads)
Maximum possible memory usage: 1.2G (14% of installed RAM)
Slow queries: 1% (4/49M)
Highest usage of available connections: 26% (38/151)
Key buffer size / total MyISAM indexes: 8.0M/1.0M
Key buffer hit rate: 98% (630 cached / 9 reads)
Query cache efficiency: 0% (0 cached / 47M selects)
Query cache prunes per day: 0
Sorts requiring temporary tables: 1% (2K temp sorts / 377K sorts)
Joins performed without indexes: 13254
Temporary tables created on disk: 3% (2K on disk / 79K total)
Thread cache hit rate: 99% (41 created / 38K connections)
Table cache hit rate: 26% (2K open / 7K opened)
Open file limit used: 0% (10/6K)
Table locks acquired immediately: 100% (682 immediate / 682 locks)
InnoDB data size / buffer pool: 687.0M/1.0G
Run OPTIMIZE TABLE to defragment tables for better performance
Adjust your join queries to always utilize indexes
query_cache_limit (> 1M, or use smaller result sets)
join_buffer_size (> 256.0K, or always use indexes with joins)
Scan Completed at Friday, 16 November 2018 6:13:44 AM

顯示全球狀態-> 1天正常運行時間

顯示全球變量-> 1天正常運行時間

Answer 1

建議考慮立即救濟

SET GLOBAL innodb_buffer_pool_size=1*1024*1024*1024

從MySQL命令提示符

將為您帶來與眾不同的世界，並可能在其他細節被整理出來的同時讓您生存。

將您的my.ini [mysqld]部分更改為1G，以進行下一次停止/啟動服務。

Answer 2

my.ini [mysqld]部分中的其他建議（每秒速率= RPS）

innodb_buffer_pool_size=2G  # from 1G reported in SHOW GLOBAL STATUS of 11/16
innodb_lru_scan_depth=100  # from 1024 to conserve CPU cycles every SECOND
thread_cache_size=100  # from 10 to increase threads_cached for increased performance
innodb_io_capacity=1600  # from 200 to allow higher IOPS 
read_rnd_buffer_size=192K  # from 256K to reduce handler_read_rnd_next RPS of 63407
innodb_log_buffer_size=16M  # from 1M for ~ 30 minutes in RAM before WD
open_files_limit=8192  # from 6209 to reduce opened_files RPHour of 152
table_open_cache=3000  # from 2000 to reduce opened_tables RPHour of 258
query_cache_size=0  # from 1M to conserve RAM since QC is OFF

如需其他幫助，請查看我的個人資料，網絡個人資料以獲取聯系信息。

如果您添加評論，請以@wilsonhauck開頭，以便SO自動提醒我。