反馈人:缪金荣
问题1:
严重级别:严重所属项目:amazon
问题原因:慢日志记录50s+,msku条件in条件量过多,并发量大,SQL(不完整):
select msku,new_value, create_time from ( select a.msku,a.new_value, a.create_time, ROW_NUMBER() OVER(PARTITION BY msku ORDER BY create_time DESC) as rownb from t_amazon_publish_execute_queue_history a join ( SELECT id FROM t_amazon_publish_execute_queue_history WHERE source_id = 10814 and 'msku' in ( '26GG9JJIJ11010JQG6KB' , 'WF530452QKWU' , 'I100E58585VLX7PT087' , '130UA0HF8I2743YCI' , 'F1031BO8JK26F0C' , '03QBK25S2206OY2A3E3L' , 'TKUA453113W' , '417H0407YP9UI' , '14DT17U9KV19GI' , '006425MMJ3X' , 'Z7004V22LB1P28TABAB' , '059937322S' , 'O115512H2KK' , '0TTT722S1572MGFH' , 'FNWW35QD12HZD16KATL6' , '53N58ZW9DA1620' , 'B21I55QEC09YUX' , 'Z649E03ZUR9D902901KIS' , 'V2841E57KH885081' , 'JO16814ZQ66ORY01P0Y9CCG' , 'L01KG721SXG3P00CCA' , 'S9352BX38P4W803GXQH9E' , 'U1311DRK4XIQ1YU539BKQUV' , '758ZIA97V05O6XB187JCNN' ,
解决方案:1、in条件数量控制在合理范围内,建议不超过100;2、并发量降低到合理范围内
问题2:
严重级别:严重
所属项目:amazon
问题原因:慢日志记录300s+,explain命中主键索引,SQL为:
SELECT
t1.id,
t1.customer_id,
t1.seller_id,
t1.source_id,
t1.strategy_id,
t1.asin,
t1.msku,
t1.sku
FROM
t_amazon_a_plus_publish_strategy_source t1
WHERE
t1.is_deleted = 0
AND t1.STATUS = 2
ORDER BY
t1.id ASC
LIMIT 500;
解决方案:1、建议增加增加查询维度来控制查询范围,比如增加source_id;2、建议指定索引,规避命中主键索引导致低效,3、建议SQL调整为select
a,b,c from t_amazon_a_plus_publish_strategy_source t join (select id
from t_amazon_a_plus_publish_strategy_source where 条件) tt on tt.id=t.id