fbpx
Unmasking Magento 2.3: How a Single Operator Escalated Database CPU Load and the Simple Fix to Reclaim Your Performance

Unmasking Magento 2.3: How a Single Operator Escalated Database CPU Load and the Simple Fix to Reclaim Your Performance

The unexpected surge in CPU load for Magento 2.3 sales software was caused by a cache issue linked to frequently searched terms. The culprit was a 'SELECT DISTINCT' operator within a lengthy query. This caused a bottleneck leading to an alarming increase in query duration from 2ms to 700ms. However, the fix was simple – removing the DISTINCT operator from the query reduced it back to 2ms, boosting Magento's performance.

This issue threatened the user experience such as search speed and page load times. Despite its consequences being felt across several Magento versions, a simple solution enormously improved query performance and reduced CPU load. This illustrates that often, simple strategies with immediate implementation can yield significant impacts.

Strategies for managing the search_query table, such as asynchronous insertion of search terms in batches, tracking only a fraction of total search terms, or disabling search term tracking, can further advance performance. Each SQL operator and condition should be carefully considered, as irrelevant ones can cause a detrimental rise in CPU load, hindering store performance.

Full article here: https://lawsuithelpdesk.com/unmasking-magento-2-3-how-a-single-operator-escalated-database-cpu-load-and-the-simple-fix-to-reclaim-your-performance/

YouTube
LinkedIn
LinkedIn
Share