mysql sqlprofile_MySQLSQL剖析(SQLprofile)

分析SQL执行带来的开销是优化SQL的重要手段。在MySQL数据库中，可以通过配置profiling参数来启用SQL剖析。该参数可以在全局和ses

分析SQL执行带来的开销是优化SQL的重要手段。在MySQL数据库中，可以通过配置profiling参数来启用SQL剖析。该参数可以在全局和session级别来设置。对于全局级别则作用于整个MySQL实例，而session级别紧影响当前session。该参数开启后，后续执行的SQL语句都将记录其资源开销，诸如IO，上下文切换，CPU，Memory等等。根据这些开销进一步分析当前SQL瓶颈从而进行优化与调整。本文描述了如何使用MySQL profile，不涉及具体的样例分析。

--------------------------------------分割线 --------------------------------------

Ubuntu 14.04下安装MySQL

《MySQL权威指南(原书第2版)》清晰中文扫描版 PDF

Ubuntu 14.04 LTS 安装 LNMP Nginx\PHP5 (PHP-FPM)\MySQL

Ubuntu 14.04下搭建MySQL主从服务器

Ubuntu 12.04 LTS 构建高可用分布式 MySQL 集群

Ubuntu 12.04下源代码安装MySQL5.6以及Python-MySQLdb

MySQL-5.5.38通用二进制安装

--------------------------------------分割线 --------------------------------------

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

--上面描述从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 |

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