MySQL SQL分析(SQL profile)

分析SQL优化运营开销SQL的重要手段。在MySQL数据库。可配置profiling参数启用SQL分析。此参数可以在全局和session水平集。级别则作用于整个MySQL实例，而session级别紧影响当前session。该參数开启后。兴许运行的SQL语句都将记录其资源开销，诸如IO，上下文切换，CPU，Memory等等。依据这些开销进一步分析当前SQL瓶颈从而进行优化与调整。本文描写叙述了怎样使用MySQL profile，不涉及详细的例子分析。

1、有关profile的描写叙述

--当前版本号

root@localhost[sakila]> show variables like 'version';

+---------------+---------------------------------------+

| Variable_name | Value                                 |

+---------------+---------------------------------------+

| version       | 5.6.17-enterprise-commercial-advanced |

+---------------+---------------------------------------+

--查看profiling系统变量

root@localhost[sakila]> show variables like '%profil%';

+------------------------+-------+

| Variable_name          | Value |

+------------------------+-------+

| have_profiling         | YES   |   --仅仅读变量。用于控制是否由系统变量开启或禁用profiling

| profiling              | OFF   |   --开启SQL语句剖析功能

| profiling_history_size | 15    |   --设置保留profiling的数目，缺省为15。范围为0至100，为0时将禁用profiling

+------------------------+-------+

profiling [539]

If set to 0 or OFF (the default), statement profiling is disabled. If set to 1 or ON, statement prof

is enabled and the SHOW PROFILE and SHOW PROFILES statements provide access to prof

information. See Section 13.7.5.32, “SHOW PROFILES Syntax”.

This variable is deprecated in MySQL 5.6.8 and will be removed in a future MySQL release.

profiling_history_size [539]

The number of statements for which to maintain profiling information if profiling [539] is

enabled. The default value is 15. The maximum value is 100. Setting the value to 0 effectively

disables profiling. See Section 13.7.5.32, “SHOW PROFILES Syntax”.

This variable is deprecated in MySQL 5.6.8 and will be removed in a future MySQL release.

--获取profile的帮助

root@localhost[sakila]> help profile;

Name: 'SHOW PROFILE'

Description:

Syntax:

SHOW PROFILE [type [, type] ... ]

    [FOR QUERY n]

    [LIMIT row_count [OFFSET offset]]

type:

    ALL                --显示全部的开销信息

  | BLOCK IO           --显示块IO相关开销

  | CONTEXT SWITCHES   --上下文切换相关开销

  | CPU                --显示CPU相关开销信息

  | IPC                --显示发送和接收相关开销信息

  | MEMORY             --显示内存相关开销信息

  | PAGE FAULTS        --显示页面错误相关开销信息

  | SOURCE             --显示和Source_function。Source_file。Source_line相关的开销信息

  | SWAPS              --显示交换次数相关开销的信息 

The SHOW PROFILE and SHOW PROFILES statements display profiling

information that indicates resource usage for statements executed

during the course of the current session.

*Note*: These statements are deprecated as of MySQL 5.6.7 and will be

removed in a future MySQL release. Use the Performance Schema instead;

see http://dev.mysql.com/doc/refman/5.6/en/performance-schema.html.

--上面描写叙述从5.6.7開始该命令将会被移除，用Performance Schema instead取代

--在Oracle数据库中。是通过autotrace来剖析单条SQL并获取真实的运行计划以及其开销信息

2、开启porfiling

--启用session级别的profiling

root@localhost[sakila]> set profiling=1;

Query OK, 0 rows affected, 1 warning (0.00 sec)

--验证改动后的结果

root@localhost[sakila]> show variables like '%profil%';

+------------------------+-------+

| Variable_name          | Value |

+------------------------+-------+

| have_profiling         | YES   |

| profiling              | ON    |

| profiling_history_size | 15    |

+------------------------+-------+

--公布SQL查询

root@localhost[sakila]> select count(*) from customer;

+----------+

| count(*) |

+----------+

|      599 |

+----------+

--查看当前session全部已产生的profile

root@localhost[sakila]> show profiles;

+----------+------------+--------------------------------+

| Query_ID | Duration   | Query                          |

+----------+------------+--------------------------------+

|        1 | 0.00253600 | show variables like '%profil%' |

|        2 | 0.00138150 | select count(*) from customer  |

+----------+------------+--------------------------------+

2 rows in set, 1 warning (0.01 sec)

--我们看到有2个warning，之前一个，如今一个

root@localhost[sakila]> show warnings;    --以下的结果表明SHOW PROFILES将来会被Performance Schema替换掉

+---------+------+--------------------------------------------------------------------------------------------------------------+

| Level   | Code | Message                                                                                                      |

+---------+------+--------------------------------------------------------------------------------------------------------------+

| Warning | 1287 | 'SHOW PROFILES' is deprecated and will be removed in a future release. Please use Performance Schema instead |

+---------+------+--------------------------------------------------------------------------------------------------------------+

3、获取SQL语句的开销信息

--能够直接使用show profile来查看上一条SQL语句的开销信息

--注。show profile之类的语句不会被profiling，即自身不会产生Profiling

--我们以下的这个show profile查看的是show warnings产生的对应开销

root@localhost[sakila]> show profile;

+----------------+----------+

| Status         | Duration |

+----------------+----------+

| starting       | 0.000141 |

| query end      | 0.000058 |

| closing tables | 0.000014 |

| freeing items  | 0.001802 |

| cleaning up    | 0.000272 |

+----------------+----------+

--如以下的查询show warnings被加入到profiles

root@localhost[sakila]> show profiles;

+----------+------------+--------------------------------+

| Query_ID | Duration   | Query                          |

+----------+------------+--------------------------------+

|        1 | 0.00253600 | show variables like '%profil%' |

|        2 | 0.00138150 | select count(*) from customer  |

|        3 | 0.00228600 | show warnings                  |

+----------+------------+--------------------------------+

--获取指定查询的开销

root@localhost[sakila]> show profile for query 2;

+----------------------+----------+

| Status               | Duration |

+----------------------+----------+

| starting             | 0.000148 |

| checking permissions | 0.000014 |

| Opening tables       | 0.000047 |

| init                 | 0.000023 |

| System lock          | 0.000035 |

| optimizing           | 0.000012 |

| statistics           | 0.000019 |

| preparing            | 0.000014 |

| executing            | 0.000006 |

| Sending data         | 0.000990 |

| end                  | 0.000010 |

| query end            | 0.000011 |

| closing tables       | 0.000010 |

| freeing items        | 0.000016 |

| cleaning up          | 0.000029 |

+----------------------+----------+

--查看特定部分的开销。例如以下为CPU部分的开销

root@localhost[sakila]> show profile cpu for query 2 ;

+----------------------+----------+----------+------------+

| Status               | Duration | CPU_user | CPU_system |

+----------------------+----------+----------+------------+

| starting             | 0.000148 | 0.000000 |   0.000000 |

| checking permissions | 0.000014 | 0.000000 |   0.000000 |

| Opening tables       | 0.000047 | 0.000000 |   0.000000 |

| init                 | 0.000023 | 0.000000 |   0.000000 |

| System lock          | 0.000035 | 0.000000 |   0.000000 |

| optimizing           | 0.000012 | 0.000000 |   0.000000 |

| statistics           | 0.000019 | 0.000000 |   0.000000 |

| preparing            | 0.000014 | 0.000000 |   0.000000 |

| executing            | 0.000006 | 0.000000 |   0.000000 |

| Sending data         | 0.000990 | 0.001000 |   0.000000 |

| end                  | 0.000010 | 0.000000 |   0.000000 |

| query end            | 0.000011 | 0.000000 |   0.000000 |

| closing tables       | 0.000010 | 0.000000 |   0.000000 |

| freeing items        | 0.000016 | 0.000000 |   0.000000 |

| cleaning up          | 0.000029 | 0.000000 |   0.000000 |

+----------------------+----------+----------+------------+

--例如以下为MEMORY部分的开销

root@localhost[sakila]> show profile memory for query 2 ;

+----------------------+----------+

| Status               | Duration |

+----------------------+----------+

| starting             | 0.000148 |

| checking permissions | 0.000014 |

| Opening tables       | 0.000047 |

| init                 | 0.000023 |

| System lock          | 0.000035 |

| optimizing           | 0.000012 |

| statistics           | 0.000019 |

| preparing            | 0.000014 |

| executing            | 0.000006 |

| Sending data         | 0.000990 |

| end                  | 0.000010 |

| query end            | 0.000011 |

| closing tables       | 0.000010 |

| freeing items        | 0.000016 |

| cleaning up          | 0.000029 |

+----------------------+----------+

--同一时候查看不同资源开销

root@localhost[sakila]> show profile block io,cpu for query 2;

+----------------------+----------+----------+------------+--------------+---------------+

| Status               | Duration | CPU_user | CPU_system | Block_ops_in | Block_ops_out |

+----------------------+----------+----------+------------+--------------+---------------+

| starting             | 0.000148 | 0.000000 |   0.000000 |            0 |             0 |

| checking permissions | 0.000014 | 0.000000 |   0.000000 |            0 |             0 |

| Opening tables       | 0.000047 | 0.000000 |   0.000000 |            0 |             0 |

| init                 | 0.000023 | 0.000000 |   0.000000 |            0 |             0 |

| System lock          | 0.000035 | 0.000000 |   0.000000 |            0 |             0 |

| optimizing           | 0.000012 | 0.000000 |   0.000000 |            0 |             0 |

| statistics           | 0.000019 | 0.000000 |   0.000000 |            0 |             0 |

| preparing            | 0.000014 | 0.000000 |   0.000000 |            0 |             0 |

| executing            | 0.000006 | 0.000000 |   0.000000 |            0 |             0 |

| Sending data         | 0.000990 | 0.001000 |   0.000000 |            0 |             0 |

| end                  | 0.000010 | 0.000000 |   0.000000 |            0 |             0 |

| query end            | 0.000011 | 0.000000 |   0.000000 |            0 |             0 |

| closing tables       | 0.000010 | 0.000000 |   0.000000 |            0 |             0 |

| freeing items        | 0.000016 | 0.000000 |   0.000000 |            0 |             0 |

| cleaning up          | 0.000029 | 0.000000 |   0.000000 |            0 |             0 |

+----------------------+----------+----------+------------+--------------+---------------+

--Author: Leshami

--Blog  : http://blog.csdn.net/leshami

--以下的SQL语句用于查询query_id为2的SQL开销，且按最大耗用时间倒序排列

root@localhost[sakila]> set @query_id=2;

root@localhost[sakila]> SELECT STATE, SUM(DURATION) AS Total_R,

    ->   ROUND(

    ->        100 * SUM(DURATION) /

    ->           (SELECT SUM(DURATION)

    ->            FROM INFORMATION_SCHEMA.PROFILING

    ->            WHERE QUERY_ID = @query_id

    ->        ), 2) AS Pct_R,

    ->     COUNT(*) AS Calls,

    ->     SUM(DURATION) / COUNT(*) AS "R/Call"

    ->  FROM INFORMATION_SCHEMA.PROFILING

    ->  WHERE QUERY_ID = @query_id

    ->  GROUP BY STATE

    ->  ORDER BY Total_R DESC;

+----------------------+----------+-------+-------+--------------+

| STATE                | Total_R  | Pct_R | Calls | R/Call       |

+----------------------+----------+-------+-------+--------------+

| Sending data         | 0.000990 | 71.53 |     1 | 0.0009900000 |--最大耗用时间部分为发送数据

| starting             | 0.000148 | 10.69 |     1 | 0.0001480000 |

| Opening tables       | 0.000047 |  3.40 |     1 | 0.0000470000 |

| System lock          | 0.000035 |  2.53 |     1 | 0.0000350000 |

| cleaning up          | 0.000029 |  2.10 |     1 | 0.0000290000 |

| init                 | 0.000023 |  1.66 |     1 | 0.0000230000 |

| statistics           | 0.000019 |  1.37 |     1 | 0.0000190000 |

| freeing items        | 0.000016 |  1.16 |     1 | 0.0000160000 |

| preparing            | 0.000014 |  1.01 |     1 | 0.0000140000 |

| checking permissions | 0.000014 |  1.01 |     1 | 0.0000140000 |

| optimizing           | 0.000012 |  0.87 |     1 | 0.0000120000 |

| query end            | 0.000011 |  0.79 |     1 | 0.0000110000 |

| end                  | 0.000010 |  0.72 |     1 | 0.0000100000 |

| closing tables       | 0.000010 |  0.72 |     1 | 0.0000100000 |

| executing            | 0.000006 |  0.43 |     1 | 0.0000060000 |

+----------------------+----------+-------+-------+--------------+

--开启profiling后。我们能够通过show profile等方式查看，事实上质是这些开销信息被记录到information_schema.profiling表

--如以下的查询，部分信息省略

profiling

root@localhost[information_schema]> select * from profiling limit 3,3\G;

*************************** 1. row ***************************

           QUERY_ID: 1

                SEQ: 5

              STATE: init

           DURATION: 0.000020

           CPU_USER: 0.000000

         CPU_SYSTEM: 0.000000

  CONTEXT_VOLUNTARY: 0

CONTEXT_INVOLUNTARY: 0

       BLOCK_OPS_IN: 0

      BLOCK_OPS_OUT: 0

      MESSAGES_SENT: 0

  MESSAGES_RECEIVED: 0

  PAGE_FAULTS_MAJOR: 0

  PAGE_FAULTS_MINOR: 0

              SWAPS: 0

    SOURCE_FUNCTION: mysql_prepare_select

        SOURCE_FILE: sql_select.cc

        SOURCE_LINE: 1050

--停止profile,能够设置profiling參数，或者在session退出之后,profiling会被自己主动关闭

root@localhost[sakila]> set profiling=off;

Query OK, 0 rows affected, 1 warning (0.00 sec)

MySQL SQL分析(SQL profile)的更多相关文章

Mysql explain分析sql语句执行效率
mysql优化–explain分析sql语句执行效率 Explain命令在解决数据库性能上是第一推荐使用命令,大部分的性能问题可以通过此命令来简单的解决,Explain可以用来查看SQL语句的执行效 ...
转://使用showplan.sql分析sql Performance
在HelloDBA网站找到一个分析sql性能的工具—showplan,记录一下 showplan.sql下载路径:http://www.HelloDBA.com/Download/showplan.z ...
mysql性能分析show profile/show profiles
MySQL性能分析show profiles show profile 和 show profiles 语句可以展示当前会话(退出session后,profiling重置为0) 中执行语句的资源使用情 ...
使用showplan.sql分析sql Performance
在HelloDBA网站找到一个分析sql性能的工具-showplan,记录一下 showplan.sql下载路径:http://www.HelloDBA.com/Download/showplan.z ...
mysql explain 分析sql语句
鉴于最近做的事情,需要解决慢sql的问题,现补充一点sql语句性能分析之explain的使用方式! 综合返回数据情况,分析各个参数,可以了解sql 使用方法:explain + sql语句如 :e ...
Mysql explain分析SQL语句之字段属性说明
在 explain的帮助下,您就知道什么时候该给表添加索引,以使用索引来查找记录从而让select 运行更快.如果由于不恰当使用索引而引起一些问题的话,可以运行 analyze table来更新该表的 ...
MySql优化分析
原理 MYSQL逻辑分层 :连接层服务层引擎层存储层 InnoDB(默认) :事务优先 (适合高并发操作:行锁) MyISAM :性能优先 (表锁) SQL优化编写过程: sql select ...
查看mysql正在执行的SQL语句，使用profile分析SQL执行状态
http://qq85609655.iteye.com/blog/2113960 1)我们先通过status命令查看Mysql运行状态 mysql> status; -------------- ...
mysql show profiles使用分析sql性能
mysql show profiles使用分析sql性能 Show profiles是5.0.37之后添加的,要想使用此功能,要确保版本在5.0.37之后. 查看一下我的数据库版本 mysql> ...

随机推荐

【安德鲁斯】基于脚本的数据库"增量更新",如果不改变，每次更新java代码、!
思维: 1.当然,它是基于SQLiteOpenHelper.onCreate(第一个呼叫建立).onUpdate(当所谓的升级计划) 2.用"脚本"(脚本制作详细方法问度娘)做数据 ...
Three.js 3D打印数据模型文件（.STL）载入中
3DPrint是现在和未来10年度科技产品的主流之中.广泛的. 对于电子商务类3D打印网站.一个主要功能就是商品3D呈现的方式,那是,3D数据可视化技术. HTML5(WebGL)它可以用于构建3D查 ...
SqlServer保留几位小数的两种做法
SqlServer保留几位小数的两种做法数据库里的 float momey 类型,都会精确到多位小数.但有时候我们不需要那么精确,例如,只精确到两位有效数字. 解决: 1. 使用 Round( ...
android 泰国/缅甸语/捷克较低，Contacts联系出现精神错乱之类的问题清单
更改ContactsProvider2.java文件 public static final String SECTION_HEADING = "SUBSTR(%1$s,1,1)" ...
EHCache的使用
在开发高并发量,高性能的网站应用系统时,缓存Cache起到了非常重要的作用.本文主要介绍EHCache的使用,以及使用EHCache的实践经验.笔者使用过多种基于Java的开源Cache组件,其中包括 ...
重新想象 Windows 8 Store Apps (12) - 控件之 GridView 特性: 拖动项, 项尺寸可变, 分组显示
原文:重新想象 Windows 8 Store Apps (12) - 控件之 GridView 特性: 拖动项, 项尺寸可变, 分组显示 [源码下载] 重新想象 Windows 8 Store Ap ...
Java 过滤器的作用
Servlet API 非常久曾经就已成为企业应用开发的基石,而 Servlet 过滤器则是对 J2EE 家族的相对较新的补充.在 J2EE 探索者系列文章的最后一篇中,作者 Kyle Gabhar ...
JAVA开源爬虫，WebCollector,使用方便，有接口。
假设你想下载整个网站内容爬行动物,我不希望配置heritrix复杂的爬行动物,要选择WebCollector.项目github一个不断更新. github源地址:https://github.com/ ...
Maven使用-利用Maven引入相关包(Struts2)
根据上一篇的项目搭建,接下来引入需要使用Struts2相关包 1,如何利用maven往项目中引入包? maven就像一个导包助手一样,让它知道去哪里拿什么,他就会自动完成需要的包的搬运工作. (1), ...
Appium0.18.x迁移到Appium1.x须知事项（灰常实用，解答了本人几个疑问）
英文原版:https://github.com/appium/appium/blob/master/docs/en/advanced-concepts/migrating-to-1-0.md Migr ...

MySQL SQL分析(SQL profile)

MySQL SQL分析(SQL profile)的更多相关文章

随机推荐

热门专题