按 Ctrl+Enter 键执行盘问按 Enter 执行盘问
| 变量 | 值 | 说明 |
|---|---|---|
Aborted clients![]() | 7 | 因客户端没有关闭毗连而中止的毗连数。。 |
Aborted connects![]() | 601.9 k | 实验毗连到 MySQL 效劳器但失败的毗连数。。 |
Access denied errors![]() | 601.8 k | |
Acl column grants![]() | 0 | |
Acl database grants![]() | 4 | |
Acl function grants![]() | 0 | |
Acl procedure grants![]() | 0 | |
Acl proxy users![]() | 1 | |
Acl role grants![]() | 0 | |
Acl roles![]() | 0 | |
Acl table grants![]() | 0 | |
Acl users![]() | 6 | |
Aria pagecache blocks not flushed![]() | 0 | |
Aria pagecache blocks unused![]() | 16 k | |
Aria pagecache blocks used![]() | 52 | |
Aria pagecache read requests![]() | 20.9 M | |
Aria pagecache reads![]() | 2.1 M | |
Aria pagecache write requests![]() | 3.5 M | |
Aria pagecache writes![]() | 0 | |
Aria transaction log syncs![]() | 0 | |
Binlog commits![]() | 0 | |
Binlog group commits![]() | 0 | |
Binlog group commit trigger count![]() | 0 | |
Binlog group commit trigger lock wait![]() | 0 | |
Binlog group commit trigger timeout![]() | 0 | |
Binlog snapshot file![]() | ||
Binlog snapshot position![]() | 0 | |
Binlog bytes written![]() | 0 | |
Binlog cache disk use![]() | 0 | 因事务使用的暂时二进制日志缓存凌驾 binlog_cache_size 的设置而使用暂时文件存储的数目。。 |
Binlog cache use![]() | 0 | 事务所用的暂时二进制日志缓存的数目。。 |
Binlog stmt cache disk use![]() | 0 | |
Binlog stmt cache use![]() | 0 | |
Busy time![]() | 0 | |
Bytes received![]() | 393.7 G | |
Bytes sent![]() | 8.6 T | |
Com admin commands![]() | 37.9 M | |
Com alter db![]() | 0 | |
Com alter db upgrade![]() | 0 | |
Com alter event![]() | 0 | |
Com alter function![]() | 0 | |
Com alter procedure![]() | 0 | |
Com alter server![]() | 0 | |
Com alter table![]() | 0 | |
Com alter tablespace![]() | 0 | |
Com analyze![]() | 0 | |
Com assign to keycache![]() | 0 | |
Com begin![]() | 0 | |
Com binlog![]() | 0 | |
Com call procedure![]() | 0 | |
Com change db![]() | 17.3 M | |
Com change master![]() | 0 | |
Com check![]() | 0 | |
Com checksum![]() | 0 | |
Com commit![]() | 0 | |
Com compound sql![]() | 0 | |
Com create db![]() | 0 | |
Com create event![]() | 0 | |
Com create function![]() | 0 | |
Com create index![]() | 0 | |
Com create procedure![]() | 0 | |
Com create role![]() | 0 | |
Com create server![]() | 0 | |
Com create table![]() | 0 | |
Com create temporary table![]() | 0 | |
Com create trigger![]() | 0 | |
Com create udf![]() | 0 | |
Com create user![]() | 0 | |
Com create view![]() | 0 | |
Com delete![]() | 12 M | |
Com delete multi![]() | 0 | |
Com do![]() | 0 | |
Com drop db![]() | 0 | |
Com drop event![]() | 0 | |
Com drop function![]() | 0 | |
Com drop index![]() | 0 | |
Com drop procedure![]() | 0 | |
Com drop role![]() | 0 | |
Com drop server![]() | 0 | |
Com drop table![]() | 0 | |
Com drop temporary table![]() | 0 | |
Com drop trigger![]() | 0 | |
Com drop user![]() | 0 | |
Com drop view![]() | 0 | |
Com empty query![]() | 0 | |
Com flush![]() | 1.5 M | |
Com get diagnostics![]() | 0 | |
Com grant![]() | 0 | |
Com grant role![]() | 0 | |
Com ha close![]() | 0 | |
Com ha open![]() | 0 | |
Com ha read![]() | 0 | |
Com help![]() | 0 | |
Com insert![]() | 10.5 M | |
Com insert select![]() | 0 | |
Com install plugin![]() | 0 | |
Com kill![]() | 0 | |
Com load![]() | 0 | |
Com lock tables![]() | 0 | |
Com optimize![]() | 0 | |
Com preload keys![]() | 0 | |
Com purge![]() | 0 | |
Com purge before date![]() | 0 | |
Com release savepoint![]() | 0 | |
Com rename table![]() | 0 | |
Com rename user![]() | 0 | |
Com repair![]() | 0 | |
Com replace![]() | 728 | |
Com replace select![]() | 0 | |
Com reset![]() | 0 | |
Com resignal![]() | 0 | |
Com revoke![]() | 0 | |
Com revoke all![]() | 0 | |
Com revoke role![]() | 0 | |
Com rollback![]() | 0 | |
Com rollback to savepoint![]() | 0 | |
Com savepoint![]() | 0 | |
Com select![]() | 3.5 G | |
Com set option![]() | 48.1 M | |
Com show authors![]() | 0 | |
Com show binlog events![]() | 0 | |
Com show binlogs![]() | 21.7 k | |
Com show charsets![]() | 0 | |
Com show collations![]() | 0 | |
Com show contributors![]() | 0 | |
Com show create db![]() | 0 | |
Com show create event![]() | 0 | |
Com show create func![]() | 0 | |
Com show create proc![]() | 0 | |
Com show create table![]() | 171.2 k | |
Com show create trigger![]() | 0 | |
Com show databases![]() | 5 | |
Com show engine logs![]() | 0 | |
Com show engine mutex![]() | 0 | |
Com show engine status![]() | 0 | |
Com show errors![]() | 0 | |
Com show events![]() | 0 | |
Com show explain![]() | 0 | |
Com show fields![]() | 1.8 M | |
Com show function status![]() | 0 | |
Com show generic![]() | 0 | |
Com show grants![]() | 41.8 k | |
Com show keys![]() | 372.3 k | |
Com show master status![]() | 44.7 k | |
Com show open tables![]() | 0 | |
Com show plugins![]() | 48.9 k | |
Com show privileges![]() | 0 | |
Com show procedure status![]() | 0 | |
Com show processlist![]() | 8 k | |
Com show profile![]() | 0 | |
Com show profiles![]() | 0 | |
Com show relaylog events![]() | 0 | |
Com show slave hosts![]() | 0 | |
Com show slave status![]() | 47.1 k | |
Com show status![]() | 22.7 k | |
Com show storage engines![]() | 51.2 k | |
Com show table status![]() | 98.5 k | |
Com show tables![]() | 660.6 k | |
Com show triggers![]() | 0 | |
Com show variables![]() | 551.9 k | |
Com show warnings![]() | 0 | |
Com shutdown![]() | 0 | |
Com signal![]() | 0 | |
Com start all slaves![]() | 0 | |
Com start slave![]() | 0 | |
Com stmt close![]() | 0 | |
Com stmt execute![]() | 0 | |
Com stmt fetch![]() | 0 | |
Com stmt prepare![]() | 0 | |
Com stmt reprepare![]() | 0 | |
Com stmt reset![]() | 0 | |
Com stmt send long data![]() | 0 | |
Com stop all slaves![]() | 0 | |
Com stop slave![]() | 0 | |
Com truncate![]() | 0 | |
Com uninstall plugin![]() | 0 | |
Com unlock tables![]() | 0 | |
Com update![]() | 9.3 M | |
Com update multi![]() | 0 | |
Com xa commit![]() | 0 | |
Com xa end![]() | 0 | |
Com xa prepare![]() | 0 | |
Com xa recover![]() | 0 | |
Com xa rollback![]() | 0 | |
Com xa start![]() | 0 | |
Compression![]() | OFF | |
Connection errors accept![]() | 0 | |
Connection errors internal![]() | 0 | |
Connection errors max connections![]() | 60 | |
Connection errors peer address![]() | 0 | |
Connection errors select![]() | 0 | |
Connection errors tcpwrap![]() | 0 | |
Connections![]() | 18.7 M | 实验毗连到 MySQL 效劳器的毗连数 (岂论乐成或失败) 。。 |
Cpu time![]() | 0 | |
Created tmp disk tables![]() | 2.2 M | 效劳器执行语句时自动在磁盘上建设的暂时表的数目。。若是 Created_tmp_disk_tables 很大,,,你可以增添 tmp_table_size 的值,,,让效劳器使用内存来存储暂时表而非磁盘。。 |
Created tmp files![]() | 5 | mysqld 已建设的暂时文件的数目。。 |
Created tmp tables![]() | 20.9 M | 效劳器执行语句时自动在内存中建设的暂时表的数目。。 |
Delayed errors![]() | 0 | 爆发过失的延迟插入 (INSERT DELAYED) 行数 (可能是由于在唯一字段中保存重复值) 。。 |
Delayed insert threads![]() | 0 | 正在使用的延迟插入处置惩罚线程的数目。。每张使用延迟插入的表都有自己的线程。。 |
Delayed writes![]() | 0 | 延迟插入已写入的行数。。 |
Delete scan![]() | 0 | |
Empty queries![]() | 25.7 M | |
Executed events![]() | 0 | |
Executed triggers![]() | 0 | |
Feature delay key write![]() | 0 | |
Feature dynamic columns![]() | 0 | |
Feature fulltext![]() | 0 | |
Feature gis![]() | 0 | |
Feature locale![]() | 0 | |
Feature subquery![]() | 2.7 M | |
Feature timezone![]() | 0 | |
Feature trigger![]() | 0 | |
Feature xml![]() | 0 | |
Flush commands![]() | 1 | 已执行的强制更新 (FLUSH) 语句数。。 |
Handler commit![]() | 7 M | 已执行的内部提交 (COMMIT) 语句数。。 |
Handler delete![]() | 6 M | 从表中删除行的次数。。 |
Handler discover![]() | 52 | 若是知道一张表的名字,,,MySQL 效劳器可以询问 NDB 集群存储引擎,,,这被称为“发明”。。Handler_discovery 批注晰一张表被发明的次数。。 |
Handler external lock![]() | 0 | |
Handler icp attempts![]() | 630.9 M | |
Handler icp match![]() | 630.9 M | |
Handler mrr init![]() | 0 | |
Handler mrr key refills![]() | 0 | |
Handler mrr rowid refills![]() | 0 | |
Handler prepare![]() | 0 | |
Handler read first![]() | 3.3 M | 读取一个索引入口点的次数。。若是该值很大,,,说明你的效劳器执行了许多完整索引扫描。。例如,,,假设字段 col1 已经建设了索引,,,然后执行 SELECT col1 FROM foo 。。 |
Handler read key![]() | 1.8 G | 凭证索引读取行的请求数。。若是该值很大,,,说明你的盘问和表都建设了很好的索引。。 |
Handler read last![]() | 17 | |
Handler read next![]() | 1.2 G | 凭证索引顺序读取下一行的请求数。。若是你在盘问一个已索引的字段且限制了规模,,,或举行完整表扫描,,,该值将会一直增添。。 |
Handler read prev![]() | 165.5 M | 凭证索引顺序读取上一行的请求数。。这种读取方法通常用于优化带有 ORDER BY … DESC 的盘问。。 |
Handler read retry![]() | 0 | |
Handler read rnd![]() | 3.2 G | 凭证牢靠位置读取行的请求数。。若是你执行许多需要排序的盘问,,,该值会很高。。你可能有许多需要完整表扫描的盘问,,,或者你使用了不准确的索引用来多表盘问。。 |
Handler read rnd deleted![]() | 4.6 M | |
Handler read rnd next![]() | 991.8 M | 从数据文件中读取行的请求数。。若是你在扫描许多表,,,该值会很大。。通常情形下这意味着你的表没有做好索引,,,或者你的盘问语句没有使用好索引字段。。 |
Handler rollback![]() | 86 | 内部回滚 (ROLLBACK) 语句数。。 |
Handler savepoint![]() | 0 | |
Handler savepoint rollback![]() | 0 | |
Handler tmp update![]() | 582.5 M | |
Handler tmp write![]() | 285.8 M | |
Handler update![]() | 4.1 M | 表中更新行的请求数。。 |
Handler write![]() | 7 M | 表中插入行的请求数。。 |
Innodb available undo logs![]() | 128 | |
Innodb background log sync![]() | 47.5 M | |
Innodb buffer pool bytes data![]() | 4.2 M | |
Innodb buffer pool bytes dirty![]() | 0 | |
Innodb buffer pool dump status![]() | Dumping buffer pool(s) not yet started | |
Innodb buffer pool load status![]() | Loading buffer pool(s) not yet started | |
Innodb buffer pool pages data![]() | 256 | 非空页数 (含脏页) 。。 |
Innodb buffer pool pages dirty![]() | 0 | 目今脏页数。。 |
Innodb buffer pool pages flushed![]() | 32.3 k | 请求更新的缓冲池页数。。 |
Innodb buffer pool pages free![]() | 766 | 空闲页数。。 |
Innodb buffer pool pages lru flushed![]() | 0 | |
Innodb buffer pool pages made not young![]() | 0 | |
Innodb buffer pool pages made young![]() | 0 | |
Innodb buffer pool pages misc![]() | 1 | 负载页的数目,,,像锁定行或顺应性的散列索引这样的治理操作时分派的页。。该值可用此公式盘算: Innodb_buffer_pool_pages_total - Innodb_buffer_pool_pages_free - Innodb_buffer_pool_pages_data 。。 |
Innodb buffer pool pages old![]() | 0 | |
Innodb buffer pool pages total![]() | 1 k | 缓冲池总巨细 (单位:页)。。 |
Innodb buffer pool read ahead![]() | 0 | |
Innodb buffer pool read ahead evicted![]() | 0 | |
Innodb buffer pool read ahead rnd![]() | 0 | InnoDB 初始化的“随机”预读数。。这通;;;;嵩诙砸徽疟砭傩写蠊婺5乃婊判蚺涛适北ⅰ! |
Innodb buffer pool read requests![]() | 32.8 M | InnoDB 完成的逻辑读请求数。。 |
Innodb buffer pool reads![]() | 4 k | InnoDB 举行逻辑读取时无法从缓冲池中获取而执行单页读取的次数。。 |
Innodb buffer pool wait free![]() | 0 | 写入 InnoDB 缓冲池通常在后台举行,,,但有须要在没有清洁页的时间读取或建设页,,,有须要先期待页被刷新。。该计数器统计了这种期待的数目。。若是缓冲池巨细设置准确,,,这个值应该会很小。。 |
Innodb buffer pool write requests![]() | 39.2 k | 写入 InnoDB 缓冲池的次数。。 |
Innodb checkpoint age![]() | 0 | |
Innodb checkpoint max age![]() | 7.8 M | |
Innodb data fsyncs![]() | 114.2 k | fsync() 总操作的次数。。 |
Innodb data pending fsyncs![]() | 0 | 目今挂起 fsync() 操作的数目。。 |
Innodb data pending reads![]() | 0 | 目今挂起的读操作数。。 |
Innodb data pending writes![]() | 0 | 目今挂起的写操作数。。 |
Innodb data read![]() | 65.2 M | 读取的总数据量 (单位:字节)。。 |
Innodb data reads![]() | 4 k | 数据读取总数。。 |
Innodb data writes![]() | 117.7 k | 数据写入总数。。 |
Innodb data written![]() | 1.1 G | 写入的总数据量 (单位:字节)。。 |
Innodb dblwr pages written![]() | 32.3 k | 以双写入操作写入的页数。。 |
Innodb dblwr writes![]() | 28.2 k | 已经执行的双写入次数。。 |
Innodb deadlocks![]() | 0 | |
Innodb have atomic builtins![]() | ON | |
Innodb history list length![]() | 1.6 k | |
Innodb ibuf discarded delete marks![]() | 0 | |
Innodb ibuf discarded deletes![]() | 0 | |
Innodb ibuf discarded inserts![]() | 0 | |
Innodb ibuf free list![]() | 0 | |
Innodb ibuf merged delete marks![]() | 0 | |
Innodb ibuf merged deletes![]() | 0 | |
Innodb ibuf merged inserts![]() | 0 | |
Innodb ibuf merges![]() | 0 | |
Innodb ibuf segment size![]() | 2 | |
Innodb ibuf size![]() | 1 | |
Innodb log waits![]() | 0 | 因日志缓存太小而必需期待其被写入所造成的期待数。。 |
Innodb log write requests![]() | 10.6 k | 日志写入请求数。。 |
Innodb log writes![]() | 29.4 k | 日志物理写入次数。。 |
Innodb lsn current![]() | 5.6 M | |
Innodb lsn flushed![]() | 5.6 M | |
Innodb lsn last checkpoint![]() | 5.6 M | |
Innodb master thread active loops![]() | 995 | |
Innodb master thread idle loops![]() | 47.5 M | |
Innodb max trx id![]() | 10.6 M | |
Innodb mem adaptive hash![]() | 297.3 k | |
Innodb mem dictionary![]() | 201.9 k | |
Innodb mem total![]() | 17.2 M | |
Innodb mutex os waits![]() | 45.9 k | |
Innodb mutex spin rounds![]() | 3.3 M | |
Innodb mutex spin waits![]() | 3.8 M | |
Innodb oldest view low limit trx id![]() | 0 | |
Innodb os log fsyncs![]() | 57.3 k | 使用 fsync() 写入日志文件的次数。。 |
Innodb os log pending fsyncs![]() | 0 | 目今挂起的 fsync 日志文件数。。 |
Innodb os log pending writes![]() | 0 | 目今挂起的日志写入数。。 |
Innodb os log written![]() | 18.1 M | 写入日志文件的字节数。。 |
Innodb page size![]() | 16.4 k | 编译的 InnoDB 页巨细 (默认 16KB)。。许多值都以页为单位举行统计,,,页巨细可以很利便地将这些值转化为字节数。。 |
Innodb pages created![]() | 88 | 建设的页数。。 |
Innodb pages read![]() | 4 k | 读取的页数。。 |
Innodb pages0 read![]() | 26 | |
Innodb pages written![]() | 32.3 k | 写入的页数。。 |
Innodb purge trx id![]() | 10.6 M | |
Innodb purge undo no![]() | 0 | |
Innodb read views memory![]() | 21 k | |
Innodb row lock current waits![]() | 0 | 正在期待行锁的数目。。 |
Innodb row lock time![]() | 3 | 期待获得行锁的总时间 (单位:毫秒)。。 |
Innodb row lock time avg![]() | 1 | 期待获得行锁的平均时间 (单位:毫秒)。。 |
Innodb row lock time max![]() | 3 | 期待获得行锁的最大时间 (单位:毫秒)。。 |
Innodb row lock waits![]() | 2 | 期待行锁的次数。。 |
Innodb rows deleted![]() | 0 | 从 InnoDB 表中删除的行数。。 |
Innodb rows inserted![]() | 2 | 插入到 InnoDB 表中的行数。。 |
Innodb rows read![]() | 184 k | 从 InnoDB 表中读取的行数。。 |
Innodb rows updated![]() | 2.1 k | InnoDB 中更新的行数。。 |
Innodb system rows deleted![]() | 0 | |
Innodb system rows inserted![]() | 0 | |
Innodb system rows read![]() | 248 | |
Innodb system rows updated![]() | 0 | |
Innodb s lock os waits![]() | 25.9 k | |
Innodb s lock spin rounds![]() | 835.5 k | |
Innodb s lock spin waits![]() | 27.9 k | |
Innodb truncated status writes![]() | 0 | |
Innodb x lock os waits![]() | 11 | |
Innodb x lock spin rounds![]() | 333 | |
Innodb x lock spin waits![]() | 2 | |
Innodb page compression saved![]() | 0 | |
Innodb page compression trim sect512![]() | 0 | |
Innodb page compression trim sect1024![]() | 0 | |
Innodb page compression trim sect2048![]() | 0 | |
Innodb page compression trim sect4096![]() | 0 | |
Innodb page compression trim sect8192![]() | 0 | |
Innodb page compression trim sect16384![]() | 0 | |
Innodb page compression trim sect32768![]() | 0 | |
Innodb num index pages written![]() | 676 | |
Innodb num non index pages written![]() | 117.1 k | |
Innodb num pages page compressed![]() | 0 | |
Innodb num page compressed trim op![]() | 0 | |
Innodb num page compressed trim op saved![]() | 0 | |
Innodb num pages page decompressed![]() | 0 | |
Innodb num pages page compression error![]() | 0 | |
Innodb num pages encrypted![]() | 0 | |
Innodb num pages decrypted![]() | 0 | |
Innodb have lz4![]() | OFF | |
Innodb have lzo![]() | OFF | |
Innodb have lzma![]() | OFF | |
Innodb have bzip2![]() | OFF | |
Innodb have snappy![]() | OFF | |
Innodb defragment compression failures![]() | 0 | |
Innodb defragment failures![]() | 0 | |
Innodb defragment count![]() | 0 | |
Innodb onlineddl rowlog rows![]() | 0 | |
Innodb onlineddl rowlog pct used![]() | 0 | |
Innodb onlineddl pct progress![]() | 0 | |
Innodb secondary index triggered cluster reads![]() | 0 | |
Innodb secondary index triggered cluster reads avoided![]() | 0 | |
Innodb encryption rotation pages read from cache![]() | 0 | |
Innodb encryption rotation pages read from disk![]() | 0 | |
Innodb encryption rotation pages modified![]() | 0 | |
Innodb encryption rotation pages flushed![]() | 0 | |
Innodb encryption rotation estimated iops![]() | 0 | |
Innodb scrub background page reorganizations![]() | 0 | |
Innodb scrub background page splits![]() | 0 | |
Innodb scrub background page split failures underflow![]() | 0 | |
Innodb scrub background page split failures out of filespace![]() | 0 | |
Innodb scrub background page split failures missing index![]() | 0 | |
Innodb scrub background page split failures unknown![]() | 0 | |
Key blocks not flushed![]() | 0 | 键缓存中还没有被写入到磁盘的键块数。。该值已往名为 Not_flushed_key_blocks 。。 |
Key blocks unused![]() | 6.4 k | 键缓存中未使用的块数。。你可以凭证这个值判断目今使用了几多键缓存。。 |
Key blocks used![]() | 7.9 k | 键缓存中已经使用的块数。。该值指示在某个时刻使用了最多块数的数目。。 |
Key blocks warm![]() | 34 | |
Key read requests![]() | 63 G | 从缓存中读取键块的请求次数。。 |
Key reads![]() | 168 | 从磁盘中物理读取键块的次数。。若是 Key_reads 很大,,,则说明您的 key_buffer_size 可能设置得太小了。;;;;捍嫒笔士梢杂 Key_reads/Key_read_requests 盘算得出。。 |
Key write requests![]() | 83 M | 将一个键块写入缓存的请求数。。 |
Key writes![]() | 63.4 M | 将键块物理写入到磁盘的次数。。 |
Last query cost![]() | 0 | 最后编译的盘问的总开销由盘问优化器盘算得出,,,可用于较量使用差别的盘问语句举行相同的盘问时的效率差别。。默认值0体现还没有盘问被编译。。 |
Master gtid wait count![]() | 0 | |
Master gtid wait time![]() | 0 | |
Master gtid wait timeouts![]() | 0 | |
Max statement time exceeded![]() | 0 | |
Max used connections![]() | 152 | 自效劳器启动以来的最高并发毗连数。。 |
Memory used![]() | 187.3 M | |
Not flushed delayed rows![]() | 0 | 期待写入延迟插入行列的行数。。 |
Open files![]() | 683 | 翻开的文件个数。。 |
Open streams![]() | 0 | 翻开的流个数 (主要用于日志纪录)。。 |
Open table definitions![]() | 132 | |
Open tables![]() | 715 | 翻开的数据表个数。。 |
Opened files![]() | 13.7 M | |
Opened plugin libraries![]() | 0 | |
Opened table definitions![]() | 131 | |
Opened tables![]() | 721 | 已经翻开的表个数。。若是该值很大,,,则说明表缓冲巨细可能设置过小。。 |
Opened views![]() | 0 | |
Performance schema accounts lost![]() | 0 | |
Performance schema cond classes lost![]() | 0 | |
Performance schema cond instances lost![]() | 0 | |
Performance schema digest lost![]() | 0 | |
Performance schema file classes lost![]() | 0 | |
Performance schema file handles lost![]() | 0 | |
Performance schema file instances lost![]() | 0 | |
Performance schema hosts lost![]() | 0 | |
Performance schema locker lost![]() | 0 | |
Performance schema mutex classes lost![]() | 0 | |
Performance schema mutex instances lost![]() | 0 | |
Performance schema rwlock classes lost![]() | 0 | |
Performance schema rwlock instances lost![]() | 0 | |
Performance schema session connect attrs lost![]() | 0 | |
Performance schema socket classes lost![]() | 0 | |
Performance schema socket instances lost![]() | 0 | |
Performance schema stage classes lost![]() | 0 | |
Performance schema statement classes lost![]() | 0 | |
Performance schema table handles lost![]() | 0 | |
Performance schema table instances lost![]() | 0 | |
Performance schema thread classes lost![]() | 0 | |
Performance schema thread instances lost![]() | 0 | |
Performance schema users lost![]() | 0 | |
Prepared stmt count![]() | 0 | |
Qcache free blocks![]() | 1 | 盘问缓存中的空闲内存块。。过多的空闲内存块可能爆发碎片,,,可通过执行 FLUSH QUERY CACHE 语句解决。。 |
Qcache free memory![]() | 1 M | 盘问缓存中空闲的内存总数。。 |
Qcache hits![]() | 0 | 缓存掷中数。。 |
Qcache inserts![]() | 0 | 加入到缓存的盘问数。。 |
Qcache lowmem prunes![]() | 0 | 为缓存新的盘问而被删除的已缓存盘问的个数,,,由最近最少使用算法 (LRU) 确定应删除哪个已缓存的盘问。。该信息可资助您调解盘问缓存巨细。。 |
Qcache not cached![]() | 0 | 未缓存的盘问数 (包括不可被缓存,,,或由于 query_cache_type 的设置而没有被缓存的盘问)。。 |
Qcache queries in cache![]() | 0 | 在缓存中注册的盘问数。。 |
Qcache total blocks![]() | 1 | 盘问缓存中的总块数。。 |
Queries![]() | 3.6 G | |
Questions![]() | 3.6 G | |
Rows read![]() | 69 G | |
Rows sent![]() | 6.4 G | |
Rows tmp read![]() | 876.2 M | |
Rpl status![]() | AUTH_MASTER | 失败;;;;て鞯淖刺 (尚未应用)。。 |
Select full join![]() | 1.3 M | 没有使用索引的多表盘问数。。若是该值不为0,,,您应该仔细检查是否已经为表建设了适当的索引。。 |
Select full range join![]() | 0 | 使用在关联表上使用规模搜索的多表盘问的数目。。 |
Select range![]() | 95.1 M | 在第一张表上使用规模盘问的多表盘问数。。(纵然该值很大,,,通常也不会有致命的影响。。) |
Select range check![]() | 0 | 没有使用索引但在每行之后检查索引使用的多表盘问数。。(若是该值不为 0,,,您应该仔细检查是否已经为表建设了适当的索引。。) |
Select scan![]() | 71.6 M | 在第一张表上举行了完整表扫描的多表盘问数。。 |
Slave connections![]() | 0 | |
Slave heartbeat period![]() | 0 | |
Slave open temp tables![]() | 0 | 目今由从 SQL 线程翻开的暂时表的数目。。 |
Slave received heartbeats![]() | 0 | |
Slave retried transactions![]() | 0 | 从 SQL 线程总共重试事务复制数。。 |
Slave running![]() | OFF | 若是该值为 ON,,,则这台效劳器是一台已经毗连到主效劳器的从效劳器。。 |
Slave skipped errors![]() | 0 | |
Slaves connected![]() | 0 | |
Slaves running![]() | 0 | |
Slow launch threads![]() | 0 | 使用了比 slow_launch_time 更多的时间来启动的线程数目。。 |
Slow queries![]() | 0 | 使用了比 long_query_time 更多时间的盘问数。。![]() |
Sort merge passes![]() | 0 | 排序算法使用合并的次数。。若是该值很大,,,您应该思量增添系统变量 sort_buffer_size 的值。。 |
Sort priority queue sorts![]() | 7.8 M | |
Sort range![]() | 789.8 M | 局部规模完成的排序次数。。 |
Sort rows![]() | 889.2 M | 排序的行数。。 |
Sort scan![]() | 17.6 M | 扫描表完成的排序次数。。 |
Ssl accept renegotiates![]() | 0 | |
Ssl accepts![]() | 0 | |
Ssl callback cache hits![]() | 0 | |
Ssl cipher![]() | ||
Ssl cipher list![]() | ||
Ssl client connects![]() | 0 | |
Ssl connect renegotiates![]() | 0 | |
Ssl ctx verify depth![]() | 0 | |
Ssl ctx verify mode![]() | 0 | |
Ssl default timeout![]() | 0 | |
Ssl finished accepts![]() | 0 | |
Ssl finished connects![]() | 0 | |
Ssl server not after![]() | ||
Ssl server not before![]() | ||
Ssl session cache hits![]() | 0 | |
Ssl session cache misses![]() | 0 | |
Ssl session cache mode![]() | NONE | |
Ssl session cache overflows![]() | 0 | |
Ssl session cache size![]() | 0 | |
Ssl session cache timeouts![]() | 0 | |
Ssl sessions reused![]() | 0 | |
Ssl used session cache entries![]() | 0 | |
Ssl verify depth![]() | 0 | |
Ssl verify mode![]() | 0 | |
Ssl version![]() | ||
Subquery cache hit![]() | 0 | |
Subquery cache miss![]() | 0 | |
Syncs![]() | 3 | |
Table locks immediate![]() | 3.6 G | 连忙需要锁定表的次数。。 |
Table locks waited![]() | 203 k | 无法连忙获得锁定表而必需期待的次数。。若是该值很高,,,且您遇到了性能方面的问题,,,则应该首先检查您的盘问语句,,,然后使用复制操作来脱离表。。 |
Tc log max pages used![]() | 0 | |
Tc log page size![]() | 0 | |
Tc log page waits![]() | 0 | |
Threadpool idle threads![]() | 0 | |
Threadpool threads![]() | 5 | |
Threads cached![]() | 0 | 线程缓存中线程的数目。;;;;捍嬷乐新士梢杂 Threads_created/Connections 盘算得出。。若是该值是红色的,,,则应该增添 thread_cache_size 的值。。 |
Threads connected![]() | 2 | 目今翻开的毗连数。。 |
Threads created![]() | 88.7 k | 目今用于控制毗连的线程数。。若是 Threads_created 很大,,,您可能需要增添 thread_cache_size 的值。。(若是线程状态优异,,,这么做通常并不会带来显著的性能提升。。) |
Threads running![]() | 1 | 非睡眠状态的线程数目。。 |
Update scan![]() | 1 | |
Uptime![]() | 552 天 17 小时,,,33 分 35 秒 | |
Uptime since flush status![]() | 552 天 17 小时,,,33 分 35 秒 | |
| Key buffer fraction % | 60.69 % | 已用键缓存百分比(盘算值) |
| Key write ratio % | 76.44 % | 物理写入数与写入请求数的百分比比值(盘算值) |
| Key read ratio % | <0.01 % | Key cache miss calculated as rate of physical reads compared to read requests (calculated value) |
| Threads cache hitrate % | 99.52 % | 线程缓存掷中率 (盘算值) |