fbpx
Decoding Magento 2.3: Navigating the Database CPU Load Dilemma and the Path to a High Performance Query Structure

Decoding Magento 2.3: Navigating the Database CPU Load Dilemma and the Path to a High Performance Query Structure

The introduction of Magento 2.3 led to a surge in database CPU load, largely due to a slow query within the Popular Search Term Cache. The query, found in the search_query table, suffers in performance due to the use of the DISTINCT operator. The larger the table, the slower the query, leading to strain on the database. A workaround solution was implemented that restored performance back to pre-Magento 2.3 levels, but failed to fix the root problem. Possible permanent fixes include removing the redundant DISTINCT operator, asynchronous insertion of search terms, and reducing the number of inserted search terms. Implementing these carefully could address the trade-off between visibility and performance and contribute to more efficient database management and optimization.

Full article here: https://lawsuithelpdesk.com/decoding-magento-2-3-navigating-the-database-cpu-load-dilemma-and-the-path-to-a-high-performance-query-structure/

YouTube
LinkedIn
LinkedIn
Share