Question

我一直在尝试获取更多信息，关于如何归因于我们的mysql上运行的任何查询占用多少cpu％，但没有用。我启用了

General Log
慢日志
效果架构

但是我从这些数据源获得的数据给了我可以优化的查询，我这样做但没有可靠的方法来确定任何查询占用多少cpu％。任何正确方向的指针都会非常有用。

示例数据

常规日志

*************************** 1。排***************** **********

  event_time: 2018-03-17 13:17:52
   user_host: YYYYY[YYYYY] @  [XXX.XX.XX.XX]
   thread_id: 16850427
   server_id: 122252267
command_type: Query
    argument: UPDATE inventory_details AS did1 INNER JOIN ( SELECT MAX(id) max_id FROM daily_inventory_details WHERE shop_id = '1160' AND inventory_item_id = 3461 GROUP BY shop_id, inventory_item_id) did2 ON did1.id = did2.max_id SET ideal = ideal + 0.071, updated_at = NOW()

慢速记录

*************************** 21。排***************** **********

2018-03-17 21:03:39
00:00:01
SELECT did1.id, smii.price, did1.count_unit, did1.count_order, did1.portion_unit, did1.portion_count, did1.beginning, did1.ist, did1.deliveries_local, did1.deliveries_own, did1.ending, did1.ideal, did1.waste FROM inventory_details did1 INNER JOIN( SELECT MAX(id) max_id FROM inventory_details WHERE shop_id = '1199' GROUP BY shop_id, inventory_item_id) did2 ...

效果架构

*************************** 1。排***************** **********

    SCHEMA_NAME: faasos_platform
                     DIGEST: ae1de22d8ed625ed3e9547cbaa89c5d3
                DIGEST_TEXT: SET `time_zone` = ? 
                 COUNT_STAR: 3885851
             SUM_TIMER_WAIT: 161144275036000
             MIN_TIMER_WAIT: 14549000
             AVG_TIMER_WAIT: 41469000
             MAX_TIMER_WAIT: 19984412000
              SUM_LOCK_TIME: 9833622000000
                 SUM_ERRORS: 0
               SUM_WARNINGS: 0
          SUM_ROWS_AFFECTED: 0
              SUM_ROWS_SENT: 0
          SUM_ROWS_EXAMINED: 0
SUM_CREATED_TMP_DISK_TABLES: 0
     SUM_CREATED_TMP_TABLES: 0
       SUM_SELECT_FULL_JOIN: 0
 SUM_SELECT_FULL_RANGE_JOIN: 0
           SUM_SELECT_RANGE: 0
     SUM_SELECT_RANGE_CHECK: 0
            SUM_SELECT_SCAN: 0
      SUM_SORT_MERGE_PASSES: 0
             SUM_SORT_RANGE: 0
              SUM_SORT_ROWS: 0
              SUM_SORT_SCAN: 0
          SUM_NO_INDEX_USED: 0
     SUM_NO_GOOD_INDEX_USED: 0
                 FIRST_SEEN: 2017-10-25 02:11:32
                  LAST_SEEN: 2018-03-17 22:04:36

额外注意

能够将CPU％的减少增加归因于查询的用法之一是在早上2:15将RCA增加此cpu％。