MySQL社区
标题:
MysqlReport分析COM_占比过高的问题
[打印本页]
作者:
oxygenant
时间:
2014-3-29 02:05
标题:
MysqlReport分析COM_占比过高的问题
刚刚用MysqlReport分析了一下,发现COM_类查询占比高达56%,看过mysqlreport指南说这个值过高是有问题的,那位能帮忙分析一下是什么问题:
MySQL 5.1.63-log uptime 6 9:41:9 Sat Mar 29 01:07:43 2014
__ Key _________________________________________________________________
Buffer used 13.33M of 256.00M %Used: 5.21
Current 60.01M %Usage: 23.44
Write hit 9.72%
Read hit 99.15%
__ Questions ___________________________________________________________
Total 972.45k 1.8/s
Com_ 553.39k 1.0/s %Total: 56.91
DMS 417.59k 0.8/s 42.94
QC Hits 1.01k 0.0/s 0.10
COM_QUIT 520 0.0/s 0.05
-Unknown 57 0.0/s 0.01
Slow 2 s 6 0.0/s 0.00 %DMS: 0.00 Log: ON
DMS 417.59k 0.8/s 42.94
SELECT 353.65k 0.6/s 36.37 84.69
INSERT 40.65k 0.1/s 4.18 9.73
UPDATE 23.23k 0.0/s 2.39 5.56
DELETE 59 0.0/s 0.01 0.01
REPLACE 0 0/s 0.00 0.00
Com_ 553.39k 1.0/s 56.91
set_option 326.10k 0.6/s 33.53
rollback 162.31k 0.3/s 16.69
commit 63.88k 0.1/s 6.57
__ SELECT and Sort _____________________________________________________
Scan 1.22k 0.0/s %SELECT: 0.34
Range 0 0/s 0.00
Full join 0 0/s 0.00
Range check 0 0/s 0.00
Full rng join 0 0/s 0.00
Sort scan 62 0.0/s
Sort range 0 0/s
Sort mrg pass 0 0/s
__ Query Cache _________________________________________________________
Memory usage 137.54k of 128.00M %Used: 0.10
Block Fragmnt 11.88%
Hits 1.01k 0.0/s
Inserts 48.35k 0.1/s
Insrt
rune 48.35k:1 0.1/s
Hit:Insert 0.02:1
__ Table Locks _________________________________________________________
Waited 17 0.0/s %Total: 0.01
Immediate 161.45k 0.3/s
__ Tables ______________________________________________________________
Open 46 of 512 %Cache: 8.98
Opened 53 0.0/s
__ Connections _________________________________________________________
Max used 13 of 2000 %Max: 0.65
Total 528 0.0/s
__ Created Temp ________________________________________________________
Disk table 51 0.0/s
Table 1.11k 0.0/s Size: 64.0M
File 5 0.0/s
__ Threads _____________________________________________________________
Running 1 of 13
Cached 0 of 4 %Hit: 67.99
Created 169 0.0/s
Slow 0 0/s
__ Aborted _____________________________________________________________
Clients 11 0.0/s
Connects 41 0.0/s
__ Bytes _______________________________________________________________
Sent 142.73M 258.0/s
Received 40.56M 73.3/s
__ InnoDB Buffer Pool __________________________________________________
Usage 304.00k of 8.00M %Used: 3.71
Read hit 84.42%
Pages
Free 493 %Total: 96.29
Data 19 3.71 %Drty: 0.00
Misc 0 0.00
Latched 0.00
Reads 77 0.0/s
From file 12 0.0/s 15.58
Ahead Rnd 1 0.0/s
Ahead Sql 0 0/s
Writes 0 0/s
Flushes 0 0/s
Wait Free 0 0/s
__ InnoDB Lock _________________________________________________________
Waits 0 0/s
Current 0
Time acquiring
Total 0 ms
Average 0 ms
Max 0 ms
__ InnoDB Data, Pages, Rows ____________________________________________
Data
Reads 25 0.0/s
Writes 3 0.0/s
fsync 3 0.0/s
Pending
Reads 0
Writes 0
fsync 0
Pages
Created 0 0/s
Read 19 0.0/s
Written 0 0/s
Rows
Deleted 0 0/s
Inserted 0 0/s
Read 0 0/s
Updated 0 0/s
作者:
oxygenant
时间:
2014-3-29 10:35
{:soso_e154:},有不少人看,怎么每人回复啊,是太简单了不屑么。。。
作者:
kider
时间:
2014-3-31 18:07
看不习惯...
貌似没啥问题,你用的是那种表引擎?InnoDB Buffer Pool 8M?连接数也不高...
作者:
nycle
时间:
2014-3-31 23:23
Com_下的rollback占比偏高,建议分析一下:业务、数据,以及错误日志。
欢迎光临 MySQL社区 (http://www.mysqlpub.com/)
Powered by Discuz! X3.2