Skip to content
Lawsuit Help Desk

Lawsuit News Center

Decoding Magento 2.3's Database CPU Overload: Unraveling the Root Cause and Ingenious Solutions

Decoding Magento 2.3’s Database CPU Overload: Unraveling the Root Cause and Ingenious Solutions

The recent update to Magento 2.3 presented a tech challenge: increased database CPU load, slowing system efficiency due to a new query – SELECT DISTINCT COUNT(*) FROM 'search_query' AS 'main_table' WHERE (main_table.store_id = 1) AND (num_results > 0). This query's execution time grows as the search_query table expands, raising the CPU load. The issue lies in the num_results > 0 condition, extending query time and causing the CPU overload. The challenge is deciding whether to remove this condition, risking the retrieval of irrelevant search terms in the cache, to boost performance. Possible solutions like adding an index to the search_query table or overriding the execute function in Magento_CatalogSearch/Controller/Result/Index could help, but need proper testing. Despite these problems, the Magento community is preparing to overcome with strategic solutions and a concentration on long-lasting fixes.

Full article here: https://medium.com/@lawsuithelpdesk/decoding-magento-2-3s-database-cpu-overload-unraveling-the-root-cause-and-ingenious-solutions-8e4d0c2de168