用show profile查询工具指定具体的type

show profile在mysql5.7之后过时

show profile命令用于跟踪执行过的sql语句的资源消耗信息,可以帮助查看sql语句的执行情况,可以在做性能分析或者问题诊断的时候作为参考。在MySQL5.7中, show profile命令已经开始不推荐使用,MySQL使用performance_schema 中系统表的信息来替代show profile命令,这儿主要是研究资源性能监控的思路。

SHOW PROFILE [type [, type] ... ]
[FOR QUERY n]
[LIMIT row_count [OFFSET offset]] type:
ALL
| BLOCK IO
| CONTEXT SWITCHES
| CPU
| IPC
| MEMORY
| PAGE FAULTS
| SOURCE
| SWAPS

此工具默认是禁用的,首先打开show profile跟踪记录SQL执行情况的配置,可以通过服务器变量在会话级别动态的修改:

mysql> set profiling = 1;
Query OK, 0 rows affected, 1 warning (0.00 sec)

当设置完成之后,在服务器上执行的所有语句,都会测量其耗费的时间和其他一些查询执行状态变更相关的数据。

以下面查询语句举例:

mysql> select * from emp;
+-------+--------+-----------+------+------------+---------+---------+--------+
| empno | ename | job | mgr | hiredate | sal | comm | deptno |
+-------+--------+-----------+------+------------+---------+---------+--------+
| 7369 | SMITH | CLERK | 7902 | 1980-12-17 | 800.00 | NULL | 20 |
| 7499 | ALLEN | SALESMAN | 7698 | 1981-02-20 | 1600.00 | 300.00 | 30 |
| 7521 | WARD | SALESMAN | 7698 | 1981-02-22 | 1250.00 | 500.00 | 30 |
| 7566 | JONES | MANAGER | 7839 | 1981-04-02 | 2975.00 | NULL | 20 |
| 7654 | MARTIN | SALESMAN | 7698 | 1981-09-28 | 1250.00 | 1400.00 | 30 |
| 7698 | BLAKE | MANAGER | 7839 | 1981-05-01 | 2850.00 | NULL | 30 |
| 7782 | CLARK | MANAGER | 7839 | 1981-06-09 | 2450.00 | NULL | 10 |
| 7788 | SCOTT | ANALYST | 7566 | 1987-07-13 | 3000.00 | NULL | 20 |
| 7839 | KING | PRESIDENT | NULL | 1981-11-17 | 5000.00 | NULL | 10 |
| 7844 | TURNER | SALESMAN | 7698 | 1981-09-08 | 1500.00 | 0.00 | 30 |
| 7876 | ADAMS | CLERK | 7788 | 1987-07-13 | 1100.00 | NULL | 20 |
| 7900 | JAMES | CLERK | 7698 | 1981-12-03 | 950.00 | NULL | 30 |
| 7902 | FORD | ANALYST | 7566 | 1981-12-03 | 3000.00 | NULL | 20 |
| 7934 | MILLER | CLERK | 7782 | 1982-01-23 | 1300.00 | NULL | 10 |
+-------+--------+-----------+------+------------+---------+---------+--------+
14 rows in set (0.01 sec)

在mysql的命令行模式下只能显示两位小数的时间,可以使用如下命令查看具体的执行时间

mysql> show profiles;
+----------+------------+-------------------+
| Query_ID | Duration | Query |
+----------+------------+-------------------+
| 1 | 0.00130500 | show databases |
| 2 | 0.00010250 | SELECT DATABASE() |
| 3 | 0.00027500 | show databases |
| 4 | 0.00023075 | show tables |
| 5 | 0.00041800 | show databases |
| 6 | 0.00018925 | show tables |
| 7 | 0.00376825 | select * from emp |
+----------+------------+-------------------+
7 rows in set, 1 warning (0.00 sec)

上面一共有7条sql语句操作,执行如下命令可以查看详细的每个步骤的时间,这儿以Query_ID = 1的语句举例子:

mysql> show profile for query 1 ;
+----------------------+----------+
| Status | Duration |
+----------------------+----------+
| starting | 0.000089 |
| checking permissions | 0.000025 |
| Opening tables | 0.000062 |
| init | 0.000036 |
| System lock | 0.000007 |
| optimizing | 0.000004 |
| statistics | 0.000023 |
| preparing | 0.000039 |
| executing | 0.000910 |
| Sending data | 0.000019 |
| end | 0.000016 |
| query end | 0.000006 |
| closing tables | 0.000002 |
| removing tmp table | 0.000004 |
| closing tables | 0.000016 |
| freeing items | 0.000013 |
| cleaning up | 0.000036 |
+----------------------+----------+
17 rows in set, 1 warning (0.00 sec)

除了query n指定Query_ID外,还可以设置Type查看MYSQL语句执行的其他信息,type主要参数如下:

all:显示所有性能信息

block io:显示块io操作的次数

context switches:显示上下文切换次数,被动和主动

cpu:显示用户cpu时间、系统cpu时间

IPC:显示发送和接受的消息数量

Memory:暂未实现

page faults:显示页错误数量

source:显示源码中的函数名称与位置

swaps:显示swap的次数

##all显示内容太宽,这儿暂不显示
mysql> show profile all for query 7;

block io

# block io
mysql> mysql> show profile block io fo 7;
+----------------------+----------+--------------+---------------+
| Status | Duration | Block_ops_in | Block_ops_out |
+----------------------+----------+--------------+---------------+
| starting | 0.000053 | 0 | 0 |
| checking permissions | 0.000006 | 0 | 0 |
| Opening tables | 0.000014 | 0 | 0 |
| init | 0.000056 | 0 | 0 |
| System lock | 0.000055 | 0 | 0 |
| optimizing | 0.000006 | 0 | 0 |
| statistics | 0.000008 | 0 | 0 |
| preparing | 0.000007 | 0 | 0 |
| executing | 0.000002 | 0 | 0 |
| Sending data | 0.003099 | 0 | 0 |
| end | 0.000006 | 0 | 0 |
| query end | 0.000007 | 0 | 0 |
| closing tables | 0.000006 | 0 | 0 |
| freeing items | 0.000396 | 0 | 0 |
| cleaning up | 0.000050 | 0 | 0 |
+----------------------+----------+--------------+---------------+
15 rows in set, 1 warning (0.00 sec)

context switches

#context switches
mysql> show profile context switches for query 1;
+----------------------+----------+-------------------+---------------------+
| Status | Duration | Context_voluntary | Context_involuntary |
+----------------------+----------+-------------------+---------------------+
| starting | 0.000089 | 0 | 0 |
| checking permissions | 0.000025 | 0 | 0 |
| Opening tables | 0.000062 | 0 | 0 |
| init | 0.000036 | 0 | 0 |
| System lock | 0.000007 | 0 | 0 |
| optimizing | 0.000004 | 0 | 0 |
| statistics | 0.000023 | 0 | 0 |
| preparing | 0.000039 | 0 | 0 |
| executing | 0.000910 | 0 | 0 |
| Sending data | 0.000019 | 0 | 0 |
| end | 0.000016 | 0 | 0 |
| query end | 0.000006 | 0 | 0 |
| closing tables | 0.000002 | 0 | 0 |
| removing tmp table | 0.000004 | 0 | 0 |
| closing tables | 0.000016 | 0 | 0 |
| freeing items | 0.000013 | 0 | 0 |
| cleaning up | 0.000036 | 0 | 0 |
+----------------------+----------+-------------------+---------------------+
17 rows in set, 1 warning (0.00 sec)

cpu

#cpu
mysql> show profile cpu for query 7;
+----------------------+----------+----------+------------+
| Status | Duration | CPU_user | CPU_system |
+----------------------+----------+----------+------------+
| starting | 0.000053 | 0.000000 | 0.000000 |
| checking permissions | 0.000006 | 0.000000 | 0.000000 |
| Opening tables | 0.000014 | 0.000000 | 0.000000 |
| init | 0.000056 | 0.000000 | 0.000000 |
| System lock | 0.000055 | 0.000000 | 0.000000 |
| optimizing | 0.000006 | 0.000000 | 0.000000 |
| statistics | 0.000008 | 0.000000 | 0.000000 |
| preparing | 0.000007 | 0.000000 | 0.000000 |
| executing | 0.000002 | 0.000000 | 0.000000 |
| Sending data | 0.003099 | 0.002000 | 0.000000 |
| end | 0.000006 | 0.000000 | 0.000000 |
| query end | 0.000007 | 0.000000 | 0.000000 |
| closing tables | 0.000006 | 0.000000 | 0.000000 |
| freeing items | 0.000396 | 0.001000 | 0.000000 |
| cleaning up | 0.000050 | 0.000000 | 0.000000 |
+----------------------+----------+----------+------------+
15 rows in set, 1 warning (0.00 sec)

ipc

#ipc
mysql> show profile ipc for query 1;
+----------------------+----------+---------------+-------------------+
| Status | Duration | Messages_sent | Messages_received |
+----------------------+----------+---------------+-------------------+
| starting | 0.000089 | 0 | 0 |
| checking permissions | 0.000025 | 0 | 0 |
| Opening tables | 0.000062 | 0 | 0 |
| init | 0.000036 | 0 | 0 |
| System lock | 0.000007 | 0 | 0 |
| optimizing | 0.000004 | 0 | 0 |
| statistics | 0.000023 | 0 | 0 |
| preparing | 0.000039 | 0 | 0 |
| executing | 0.000910 | 0 | 0 |
| Sending data | 0.000019 | 0 | 0 |
| end | 0.000016 | 0 | 0 |
| query end | 0.000006 | 0 | 0 |
| closing tables | 0.000002 | 0 | 0 |
| removing tmp table | 0.000004 | 0 | 0 |
| closing tables | 0.000016 | 0 | 0 |
| freeing items | 0.000013 | 0 | 0 |
| cleaning up | 0.000036 | 0 | 0 |
+----------------------+----------+---------------+-------------------+
17 rows in set, 1 warning (0.00 sec)

page faults

# page faults
mysql> show profile page faults for query 1;
+----------------------+----------+-------------------+-------------------+
| Status | Duration | Page_faults_major | Page_faults_minor |
+----------------------+----------+-------------------+-------------------+
| starting | 0.000089 | 0 | 0 |
| checking permissions | 0.000025 | 0 | 0 |
| Opening tables | 0.000062 | 0 | 0 |
| init | 0.000036 | 0 | 0 |
| System lock | 0.000007 | 0 | 0 |
| optimizing | 0.000004 | 0 | 0 |
| statistics | 0.000023 | 0 | 0 |
| preparing | 0.000039 | 0 | 0 |
| executing | 0.000910 | 0 | 1 |
| Sending data | 0.000019 | 0 | 0 |
| end | 0.000016 | 0 | 0 |
| query end | 0.000006 | 0 | 0 |
| closing tables | 0.000002 | 0 | 0 |
| removing tmp table | 0.000004 | 0 | 0 |
| closing tables | 0.000016 | 0 | 0 |
| freeing items | 0.000013 | 0 | 0 |
| cleaning up | 0.000036 | 0 | 0 |
+----------------------+----------+-------------------+-------------------+
17 rows in set, 1 warning (0.00 sec)

source

swaps

# swaps
mysql> show profile swaps for query 7;
+----------------------+----------+-------+
| Status | Duration | Swaps |
+----------------------+----------+-------+
| starting | 0.000053 | 0 |
| checking permissions | 0.000006 | 0 |
| Opening tables | 0.000014 | 0 |
| init | 0.000056 | 0 |
| System lock | 0.000055 | 0 |
| optimizing | 0.000006 | 0 |
| statistics | 0.000008 | 0 |
| preparing | 0.000007 | 0 |
| executing | 0.000002 | 0 |
| Sending data | 0.003099 | 0 |
| end | 0.000006 | 0 |
| query end | 0.000007 | 0 |
| closing tables | 0.000006 | 0 |
| freeing items | 0.000396 | 0 |
| cleaning up | 0.000050 | 0 |
+----------------------+----------+-------+
15 rows in set, 1 warning (0.00 sec)

MySQL调优性能监控之show profile的更多相关文章

  1. MySQL调优性能监控之performance schema

    一.performance_schema的介绍 performance:性能 schema:图(表)示,以大纲或模型的形式表示计划或理论. MySQL的performance schema 用于监控M ...

  2. MySQL(调优慢查询、explain profile) 转

    转自http://www.linuxidc.com/Linux/2012-09/70459.htm mysql profile explain slow_query_log分析优化查询 在做性能测试中 ...

  3. MySQL调优用户监控之show processlist

    简介 show processlist显示这台MySQL正在连接的用户: mysql> show processlist; +----+------+-----------+-------+-- ...

  4. MySQL 调优/优化的 100 个建议

    MySQL 调优/优化的 100 个建议   MySQL是一个强大的开源数据库.随着MySQL上的应用越来越多,MySQL逐渐遇到了瓶颈.这里提供 101 条优化 MySQL 的建议.有些技巧适合特定 ...

  5. mysql调优学习笔记

    性能监控 使用show profile查询剖析工具,可以指定具体的type 此工具默认是禁用的,可以通过服务器变量在绘画级别动态的修改 set profiling=1; 当设置完成之后,在服务器上执行 ...

  6. MySQL 调优基础(一) CPU与进程

    一般而言,MySQL 的调优可以分为两个层面,一个是在MySQL层面上进行的调优,比如SQL改写,索引的添加,MySQL各种参数的配置:另一个层面是从操作系统的层面和硬件的层面来进行调优.操作系统的层 ...

  7. MySQL调优系列基础篇

    前言 有一段时间没有写博客了,整天都在忙,上班,录制课程,恰巧最近一段时间比较清闲,打算弄弄MYSQL数据库. 关于MySQL数据库,这里就不做过多的介绍,开源.免费等特性深受各个互联网行业喜爱,尤其 ...

  8. mysql调优 基础

    MySQL调优可以从几个方面来做: 1. 架构层:做从库,实现读写分离: 2.系统层次:增加内存:给磁盘做raid0或者raid5以增加磁盘的读写速度:可以重新挂载磁盘,并加上noatime参数,这样 ...

  9. MySQL调优 —— Using temporary

      DBA发来一个线上慢查询问题. SQL例如以下(为突出重点省略部分内容): select distinct article0_.id, 等字段 from article_table article ...

随机推荐

  1. 【进程/作业管理】篇章一:Linux进程及其管理(系统监控类工具)----glances、dstat

    glances   dstat   glances命令详解 相对于htop工具的使用,这里介绍一下glances工具的使用,我个人是比较喜欢这款工具的,主要就是由于glances这款工具可以将系统状态 ...

  2. 机器学习-决策树之ID3算法

    概述 决策树(Decision Tree)是一种非参数的有监督学习方法,它是一种树形结构,所以叫决策树.它能够从一系列有特征和标签的数据中总结出决策规则,并用树状图的结构来呈现这些规则,以解决分类和回 ...

  3. Error:(18) error: '#FFFF782' is incompatible with attribute android:endColor (attr) color. --Android

    android  studio 编译是报如下错误: Error:(18) error: '#FFFF782' is incompatible with attribute android:endCol ...

  4. sql去除重复的几种方法

    所以用这样一句SQL就可以去掉重复项了: select * from msg group by terminal_id; SQL中distinct的用法(四种示例分析) 示例1 select dist ...

  5. PP主数据-物料主数据

    一.PP物料主数据:PP的物料主数据,是对应到系统的组织架构的,不同的组织层次,都有各自的主数据需要创建. (1),一般数据:一般数据是在集团层面的主数据,主要包括:物料编码.物料描述.辅助计量单位以 ...

  6. [leetcode]109. Convert Sorted List to Binary Search Tree链表构建二叉搜索树

    二叉树的各种遍历方式都是可以建立二叉树的,例如中序遍历,就是在第一步建立左子树,中间第二步建立新的节点,第三步构建右子树 此题利用二叉搜索树的中序遍历是递增序列的特点,而链表正好就是递增序列,从左子树 ...

  7. Linux嵌入式学习-ds18b20驱动

    ds18b20的时序图如下: 复位时序: 读写时序: 以下是程序代码: #include <linux/module.h> #include <linux/init.h> #i ...

  8. Linux嵌入式学习-交叉编译mplayer

    http://bbs.gkong.com/archive.aspx?ID=286721

  9. stm32学习笔记之SysTick的思考

    原文来自--SevenZ的笔记.http://blog.21ic.com/user1/8247/archives/2011/85920.html ? 首先我们要明白什么是SysTick定时器? Sys ...

  10. dp的冗余(选数类)

    我们先来看一个例题: 在一个长度为n的序列中选出任意个数的数,要求每m个数中至少一个被选,要求选的数之和最小化. 我们很容易想出用f[i][j]来表示前i个数选的最后一个数是j,也就有 for(int ...