EC2 t3.medium 实例 CPU 峰值 +90% 有时 [已关闭]

EC2 t3.medium instance CPU spikes +90% sometimes [closed]

提问人:john 提问时间:10/7/2023 最后编辑:john 更新时间:10/7/2023 访问量:72

问:


这个问题似乎不是关于特定的编程问题、软件算法或程序员主要使用的软件工具。如果您认为该问题在另一个 Stack Exchange 站点上是主题,您可以发表评论以解释该问题可能在哪里得到回答。

上个月关闭。

实例详细信息:

Type: t3.medium
vCPUs: 2
RAM: 4
OS: Rocky Linux 9

本周每小时最大 CPU 使用率:屏幕截图

Cpanel 随 PHP 8.2 MYSQL 8.0.34 一起安装

当前内存和 CPU 使用率(输出):top

top - 13:07:30 up 1 day,  8:39,  1 user,  load average: 0.18, 0.17, 0.25
Tasks: 165 total,   1 running, 158 sleeping,   0 stopped,   6 zombie
%Cpu(s): 12.0 us,  2.8 sy,  0.0 ni, 81.7 id,  0.0 wa,  0.3 hi,  0.2 si,  3.0 st
MiB Mem :   3602.2 total,    829.4 free,   1365.9 used,   1728.8 buff/cache
MiB Swap:   1024.0 total,   1011.5 free,     12.5 used.   2236.3 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  58342 mysql     20   0 1470328 273704  33368 S   0.7   7.4   4:06.57 mysqld
  60929 dovecot   20   0    8252   4532   3832 S   0.3   0.1   0:03.55 auth
  61170 cpanelc+  20   0    6780   3968   3440 S   0.3   0.1   1:35.05 p0f
      1 root      20   0  104508  14064   9996 S   0.0   0.4   1:21.07 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.03 kthreadd
      3 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_gp
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_par+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 slub_fl+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 netns
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     10 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 mm_perc+
     12 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+
     13 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+
     14 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+
     15 root      20   0       0      0      0 S   0.0   0.0   0:00.84 ksoftir+
     16 root      20   0       0      0      0 I   0.0   0.0   0:13.71 rcu_pre+
     17 root      rt   0       0      0      0 S   0.0   0.0   0:00.70 migrati+

该网站是一个在线测试平台,用户可以使用 AJAX 逐个问题提交测试问题,因此每个用户每分钟可以提交大约 20-40 个问题,持续大约 45 分钟。上面的 CPU 统计信息主要来自访客访问者,而不是提交问题的用户,因此实例无法处理大约 1000 名访问者有点奇怪,也许 CPU 峰值是因为另一个进程,而不是用户。

我们预计很快会有更多的流量和用户,因此我们正在考虑以下解决方案之一:

1- 升级到 t3.large 或 c5a.large。

2- 创建一个自动扩展组,其中包含 2 个 t3.medium,以防 CPU > 90%。

CPU 使用率是否仅与 vCPU 数量有关?如果是这样,使用具有 4 个 vCPU 和 16GB RAM 的实例会更好吗?

关于MYSQL的更新A- 从 information_schema.tables 中选择 COUNT(*):718

D- 显示完整流程列表:

Id   User  Host      db      Command  Time  State 
2830 user  localhost dbname  Query    0     init
2831 user  localhost NULL    Sleep    0     NULL

E- 状态:#1064 - 您的 SQL 语法有错误;检查与您的MySQL服务器版本相对应的手册,了解在第1行的“STATUS”附近使用的正确语法

G- SHOW ENGINE INNODB 状态:

=====================================
2023-10-07 18:41:14 140318059087424 INNODB MONITOR OUTPUT
=====================================
Per second averages calculated from the last 8 seconds
-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 231 srv_active, 0 srv_shutdown, 68899 srv_idle
srv_master_thread log flush and writes: 0
----------
SEMAPHORES
----------
OS WAIT ARRAY INFO: reservation count 150
OS WAIT ARRAY INFO: signal count 150
RW-shared spins 0, rounds 0, OS waits 0
RW-excl spins 0, rounds 0, OS waits 0
RW-sx spins 0, rounds 0, OS waits 0
Spin rounds per wait: 0.00 RW-shared, 0.00 RW-excl, 0.00 RW-sx
------------
TRANSACTIONS
------------
Trx id counter 6877688
Purge done for trx's n:o < 6877688 undo n:o < 0 state: running but idle
History list length 2
LIST OF TRANSACTIONS FOR EACH SESSION:
---TRANSACTION 421793173028056, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421793173027248, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421793173026440, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
--------
FILE I/O
--------
I/O thread 0 state: waiting for completed aio requests ((null))
I/O thread 1 state: waiting for completed aio requests (insert buffer thread)
I/O thread 2 state: waiting for completed aio requests (read thread)
I/O thread 3 state: waiting for completed aio requests (read thread)
I/O thread 4 state: waiting for completed aio requests (read thread)
I/O thread 5 state: waiting for completed aio requests (read thread)
I/O thread 6 state: waiting for completed aio requests (write thread)
I/O thread 7 state: waiting for completed aio requests (write thread)
I/O thread 8 state: waiting for completed aio requests (write thread)
Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] ,
 ibuf aio reads:
Pending flushes (fsync) log: 0; buffer pool: 0
2841 OS file reads, 16006 OS file writes, 9829 OS fsyncs
0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
-------------------------------------
INSERT BUFFER AND ADAPTIVE HASH INDEX
-------------------------------------
Ibuf: size 1, free list len 23, seg size 25, 28 merges
merged operations:
 insert 74, delete mark 1696, delete 449
discarded operations:
 insert 0, delete mark 0, delete 0
Hash table size 12821, node heap has 3 buffer(s)
Hash table size 12821, node heap has 4 buffer(s)
Hash table size 12821, node heap has 2 buffer(s)
Hash table size 12821, node heap has 7 buffer(s)
Hash table size 12821, node heap has 5 buffer(s)
Hash table size 12821, node heap has 5 buffer(s)
Hash table size 12821, node heap has 3 buffer(s)
Hash table size 12821, node heap has 3 buffer(s)
0.00 hash searches/s, 0.25 non-hash searches/s
---
LOG
---
Log sequence number          3510600244
Log buffer assigned up to    3510600244
Log buffer completed up to   3510600244
Log written up to            3510600244
Log flushed up to            3510600244
Added dirty pages up to      3510600244
Pages flushed up to          3510600244
Last checkpoint at           3510600244
Log minimum file id is       1071
Log maximum file id is       1072
6439 log i/o's done, 0.00 log i/o's/second
----------------------
BUFFER POOL AND MEMORY
----------------------
Total large memory allocated 0
Dictionary memory allocated 2226952
Buffer pool size   3135
Free buffers       1024
Database pages     2079
Old database pages 747
Modified db pages  0
Pending reads      0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 872, not young 22312
0.00 youngs/s, 0.00 non-youngs/s
Pages read 2517, created 236, written 7472
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 2079, unzip_LRU len: 0
I/O sum[0]:cur[0], unzip sum[0]:cur[0]
--------------
ROW OPERATIONS
--------------
0 queries inside InnoDB, 0 queries in queue
0 read views open inside InnoDB
Process ID=58342, Main thread ID=140317588190784 , state=sleeping
Number of rows inserted 167, updated 242, deleted 987, read 337992
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
Number of system rows inserted 125, updated 4066, deleted 119, read 146393
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.12 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================
性能 Amazon-EC2 cPanel CPU-Usage

评论

0赞 Wilson Hauck 10/7/2023
请提供其他数据库信息请求。MySQL主机服务器上是否有任何SSD或NVME设备?在 justpaste.it 上发布 TEXT 数据并分享链接。从您的 SSH 登录根目录中,文本结果如下: A) 从 information_schema.tables 中选择 COUNT(*);B) 显示全球状态;至少 24 小时后正常运行时间 C) 显示全局变量;D) 显示完整的流程列表;E) 状态;不是 SHOW STATUS,只是 STATUS;G) 显示发动机 INNODB 状态;用于服务器工作负载调优分析,提供 CPU 使用率平滑建议。
0赞 john 10/7/2023
@WilsonHauck,我用所需的大部分数据更新了问题。我将添加数字 B 和 C 的链接,因为有问题,我不能添加超过 1 个链接。
0赞 john 10/7/2023
@WilsonHauck 这是数字 B 和 C transfernow.net/dl/20231007whYwcJVR
0赞 Wilson Hauck 10/8/2023
您选择的 transfernow.net 解决方案正在敲响警钟。因此,请将 B) 和 C) 的文本结果发布到 justpaste.it,我将能够获取您的其他数据进行分析。
0赞 john 10/8/2023
全球状态:justpaste.it/c2bw8

答: 暂无答案