MYSQL查询优化:profile功能

这里还需要注意一点就是,需要安装profile模块才能实现。

1、不过版本要在5.0.37之后。(SHOW PROFILES and SHOW PROFILE were added in MySQL 5.0.37.)

SELECT @@profiling;

来查看是否已经启用profile,如果profilng值为0,可以通过

SET profiling = 1;

来启用。启用profiling之后,我们执行一条查询语句,比如:

select count(*) from roi_summary;

然后show profiles查看如下:

+----------------+------------+----------------------------------+
| Query_ID       | Duration   | Query                            |
+----------------+------------+----------------------------------+
|        1       | 0.00021500 | select @@profiling               |
|        2       | 0.05522700 | select count(*) from roi_summary |
+----------------+------------+----------------------------------+

2 rows in set (0.00 sec)

其中ID为5的语句是刚执行的查询语句


2、变量profiling是用户变量,每次都得重新启用。
以下是我做的一些实验。数据很明显,就不多解释了。

复制代码
mysql> use test
Database changed
mysql> set profiling=1;
Query OK, 0 rows affected (0.00 sec)

mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| bag_item | 
| bag_user | 
| score | 
| t | 
+----------------+
4 rows in set (0.03 sec)

mysql> select count(*) from t;
+----------+
| count(*) |
+----------+
| 2097152 | 
+----------+
1 row in set (0.74 sec)

mysql> show profiles;
+----------+------------+------------------------+
| Query_ID | Duration   | Query                  |
+----------+------------+------------------------+
|        1 | 0.02717000 | show tables            | 
|        2 | 0.74770100 | select count(*) from t | 
+----------+------------+------------------------+
2 rows in set (0.00 sec)

mysql> show profile for query 2;
+--------------------------------+----------+
| Status                         | Duration |
+--------------------------------+----------+
| (initialization)               | 0.000004 | 
| checking query cache for query | 0.000044 | 
| Opening tables                 | 0.000012 | 
| System lock                    | 0.000017 | 
| Table lock                     | 0.00003  | 
| init                           | 0.000013 | 
| optimizing                     | 0.000008 | 
| statistics                     | 0.000013 | 
| preparing                      | 0.000011 | 
| executing                      | 0.000006 | 
| Sending data                   | 0.747313 | 
| end                            | 0.000014 | 
| query end                      | 0.000006 | 
| storing result in query cache  | 0.000006 | 
| freeing items                  | 0.000012 | 
| closing tables                 | 0.000009 | 
| logging slow query             | 0.000183 | 
+--------------------------------+----------+
17 rows in set (0.00 sec)

mysql> show profile block io,cpu for query 2;
+--------------------------------+----------+----------+------------+--------------+---------------+
| Status                         | Duration | CPU_user | CPU_system | Block_ops_in | Block_ops_out |
+--------------------------------+----------+----------+------------+--------------+---------------+
| (initialization)               | 0.000004 | 0        | 0          |            0 |             0 | 
| checking query cache for query | 0.000044 | 0        | 0          |            0 |             0 | 
| Opening tables                 | 0.000012 | 0        | 0          |            0 |             0 | 
| System lock                    | 0.000017 | 0        | 0          |            0 |             0 | 
| Table lock                     | 0.00003  | 0        | 0          |            0 |             0 | 
| init                           | 0.000013 | 0        | 0          |            0 |             0 | 
| optimizing                     | 0.000008 | 0        | 0          |            0 |             0 | 
| statistics                     | 0.000013 | 0        | 0          |            0 |             0 | 
| preparing                      | 0.000011 | 0        | 0          |            0 |             0 | 
| executing                      | 0.000006 | 0        | 0          |            0 |             0 | 
| Sending data                   | 0.747313 | 0.746887 | 0          |            0 |             0 | 
| end                            | 0.000014 | 0        | 0          |            0 |             0 | 
| query end                      | 0.000006 | 0        | 0          |            0 |             0 | 
| storing result in query cache  | 0.000006 | 0        | 0          |            0 |             0 | 
| freeing items                  | 0.000012 | 0        | 0          |            0 |             0 | 
| closing tables                 | 0.000009 | 0        | 0          |            0 |             0 | 
| logging slow query             | 0.000183 | 0        | 0          |            0 |             0 | 
+--------------------------------+----------+----------+------------+--------------+---------------+
17 rows in set (0.00 sec)

mysql> insert into t(username) select username from t;
Query OK, 2097152 rows affected (34.17 sec)
Records: 2097152  Duplicates: 0  Warnings: 0

mysql> show profiles;
+----------+-------------+------------------------------------------------+
| Query_ID | Duration    | Query                                          |
+----------+-------------+------------------------------------------------+
|        1 |  0.02717000 | show tables                                    | 
|        2 |  0.74770100 | select count(*) from t                         | 
|        3 |  0.00004200 | show prifile for query 2                       | 
|        4 | 34.30410100 | insert into t(username) select username from t | 
+----------+-------------+------------------------------------------------+
4 rows in set (0.00 sec)

mysql> show profile cpu,block io,memory,swaps for query 4;

mysql> select count(*) from t;
+----------+
| count(*) |
+----------+
|  4194304 | 
+----------+
1 row in set (1.51 sec)

mysql> show profiles;
+----------+-------------+------------------------------------------------+
| Query_ID | Duration    | Query                                          |
+----------+-------------+------------------------------------------------+
|        1 |  0.02717000 | show tables                                    | 
|        2 |  0.74770100 | select count(*) from t                         | 
|        3 |  0.00004200 | show prifile for query 2                       | 
|        4 | 34.30410100 | insert into t(username) select username from t | 
|        5 |  1.50563800 | select count(*) from t                         | 
+----------+-------------+------------------------------------------------+
5 rows in set (0.00 sec)

mysql> show profile cpu,block io,memory,swaps,context switches,source for query 5;
……
mysql> update t set username = 'waill';
Query OK, 4194304 rows affected (44.82 sec)
Rows matched: 4194304  Changed: 4194304  Warnings: 0

mysql> show profiles;
+----------+-------------+------------------------------------------------+
| Query_ID | Duration    | Query                                          |
+----------+-------------+------------------------------------------------+
|        1 |  0.02717000 | show tables                                    | 
|        2 |  0.74770100 | select count(*) from t                         | 
|        3 |  0.00004200 | show prifile for query 2                       | 
|        4 | 34.30410100 | insert into t(username) select username from t | 
|        5 |  1.50563800 | select count(*) from t                         | 
|        6 | 44.82054700 | update t set username = 'waill'                | 
+----------+-------------+------------------------------------------------+
6 rows in set (0.00 sec)

mysql> show profile cpu,block io,memory,swaps,context switches,source for query 6;
复制代码

 

转载:http://hi.baidu.com/chssheng2007/blog/item/a97888b3e8ac0ebfd9335aae.html

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
目标检测(Object Detection)是计算机视觉领域的一个核心问题,其主要任务是找出图像中所有感兴趣的目标(物体),并确定它们的类别和位置。以下是对目标检测的详细阐述: 一、基本概念 目标检测的任务是解决“在哪里?是什么?”的问题,即定位出图像中目标的位置并识别出目标的类别。由于各类物体具有不同的外观、形状和姿态,加上成像时光照、遮挡等因素的干扰,目标检测一直是计算机视觉领域最具挑战性的任务之一。 二、核心问题 目标检测涉及以下几个核心问题: 分类问题:判断图像中的目标属于哪个类别。 定位问题:确定目标在图像中的具体位置。 大小问题:目标可能具有不同的大小。 形状问题:目标可能具有不同的形状。 三、算法分类 基于深度学习的目标检测算法主要分为两大类: Two-stage算法:先进行区域生成(Region Proposal),生成有可能包含待检物体的预选框(Region Proposal),再通过卷积神经网络进行样本分类。常见的Two-stage算法包括R-CNN、Fast R-CNN、Faster R-CNN等。 One-stage算法:不用生成区域提议,直接在网络中提取特征来预测物体分类和位置。常见的One-stage算法包括YOLO系列(YOLOv1、YOLOv2、YOLOv3、YOLOv4、YOLOv5等)、SSD和RetinaNet等。 四、算法原理 以YOLO系列为例,YOLO将目标检测视为回归问题,将输入图像一次性划分为多个区域,直接在输出层预测边界框和类别概率。YOLO采用卷积网络来提取特征,使用全连接层来得到预测值。其网络结构通常包含多个卷积层和全连接层,通过卷积层提取图像特征,通过全连接层输出预测结果。 五、应用领域 目标检测技术已经广泛应用于各个领域,为人们的生活带来了极大的便利。以下是一些主要的应用领域: 安全监控:在商场、银行
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值