MariaDB上的查询非常慢

时间:2015-12-17 13:01:02

标签: mysql mariadb

自从我开始使用MariaDB 10以来,我正面临这个问题。查询花费了太多时间。使用MySql 5.5,他们最多花了一分钟来获得结果集但是使用MariaDB我甚至无法在20分钟后看到结果集。

这个系统在Magento 1.7.0.2上运行,但这个问题与Magento无关,所以我没有在Magento部分创建它。

我的服务器管理员说“服务器上的一切正常,查询在ram上运行,cpu在此查询开始运行时是100%,如果你想改进它,你需要更改查询或增加cpu功率。 ”。但我很确定这与MariaDB和/或数据库服务器设置有关。

如果有任何人遇到过这样的问题,请引导我走正确的道路。

这是应该运行以获取用于创建Feed的数据的最大查询之一。

SELECT `e`.*, `at_status`.`value` AS `status`, `at_visibility`.`value` AS      
`visibility`, `at_quality_score`.`value` AS `quality_score`,    
`at_exportable_for_idealo`.`value` AS `exportable`, 
`stock`.`qty`, `stock`.`is_in_stock`, `stock`.`manage_stock`, 
`stock`.`use_config_manage_stock`, `stock`.`min_qty`, 
`stock`.`min_sale_qty`, MAX(DISTINCT request_path) AS `request_path`, 
`cpsl`.`parent_id`, `categories`.*, `categories_parent`.*, 
GROUP_CONCAT(DISTINCT categories_index.category_id) AS `categories_ids`, 
`price_index`.`min_price`, `price_index`.`max_price`, 
`price_index`.`tier_price`, `price_index`.`final_price` FROM 
`catalog_product_entity` AS `e`

INNER JOIN `catalog_product_website` AS `product_website` ON      
product_website.product_id = e.entity_id AND product_website.website_id =     
'1'

INNER JOIN `catalog_product_entity_int` AS `at_status` ON 
(`at_status`.`entity_id` = `e`.`entity_id`) AND (`at_status`.`attribute_id` 
= '96') AND (`at_status`.`store_id` = 0)

INNER JOIN `catalog_product_entity_int` AS `at_visibility` ON 
(`at_visibility`.`entity_id` = `e`.`entity_id`) AND 
(`at_visibility`.`attribute_id` = '102') AND (`at_visibility`.`store_id` = 
0)

INNER JOIN `catalog_product_entity_varchar` AS `at_quality_score` ON 
(`at_quality_score`.`entity_id` = `e`.`entity_id`) AND 
(`at_quality_score`.`attribute_id` = '313') AND 
(`at_quality_score`.`store_id` = 0)

INNER JOIN `catalog_product_entity_int` AS `at_exportable_for_idealo` ON 
(`at_exportable_for_idealo`.`entity_id` = `e`.`entity_id`) AND 
(`at_exportable_for_idealo`.`attribute_id` = '353') AND 
(`at_exportable_for_idealo`.`store_id` = 0)

LEFT JOIN `cataloginventory_stock_item` AS `stock` ON 
stock.product_id=e.entity_id

LEFT JOIN `core_url_rewrite` AS `url` ON url.product_id=e.entity_id AND 
url.target_path NOT LIKE '%category%' AND is_system=1 AND ISNULL(options) 
AND url.store_id=1

LEFT JOIN `catalog_product_super_link` AS `cpsl` ON 
cpsl.product_id=e.entity_id 

LEFT JOIN `catalog_category_product` AS `categories` ON 
categories.product_id=e.entity_id

LEFT JOIN `catalog_category_product` AS `categories_parent` ON 
categories_parent.product_id=cpsl.parent_id

LEFT JOIN `catalog_category_product_index` AS `categories_index` ON 
((categories_index.category_id=categories.category_id AND 
categories_index.product_id=categories.product_id) OR 
(categories_index.category_id=categories_parent.category_id AND 
categories_index.product_id=categories_parent.product_id )) AND 
categories_index.store_id=1

LEFT JOIN `catalog_product_index_price` AS `price_index` ON 
price_index.entity_id=e.entity_id AND customer_group_id=0 AND 
price_index.website_id=1 WHERE (at_status.value = '1') AND (`e`.`type_id` 
IN('simple')) AND (at_visibility.value IN('1')) AND (`e`.`attribute_set_id` 
IN('19', '13', '4')) AND ((at_quality_score.value = 'A')) AND 
((at_status.value = '1')) AND ((at_exportable_for_idealo.value = '1'))

如上所述,即使在20分钟后我也看不到结果!没有异常抛出,没有sql错误日志,没有php错误日志,没有。即使我直接在PhpMyAdmin上运行它,结果也完全相同。

提前致谢。

1 个答案:

答案 0 :(得分:0)

我没有遇到这类问题,但我确信如果你用子查询编写联接,那么它会优化

而不是

INNER JOIN catalog_product_website AS product_website ON product_website.product_id = e.entity_id AND product_website.website_id =
' 1'

写得像

INNER JOIN (从catalog_product_website中选择*  product_website.website_id =' 1')作为临时值  ON
temp.product_id = e.entity_id

如果在所有联接中更改此项,则执行查询所需的时间会更短。