fbpx
Unraveling the Mystery: How Magento 2.3's Update Unleashed a CPU Load Crisis & the Pioneering Fixes to Restore Your Site's Performance

Unraveling the Mystery: How Magento 2.3’s Update Unleashed a CPU Load Crisis & the Pioneering Fixes to Restore Your Site’s Performance

Magento 2.3's 'Popular Search Term Cache' feature resulted in a database CPU load crisis due to a problematic query, significantly impacting the performance of websites. The query in question, SELECT DISTINCT COUNT (*) FROM search_query WHERE (store_id = 1) AND (num_results > 0), affected sites with large search_query tables. This persisted even when using ElasticSearch, suggesting a Magento framework flaw. Proposed solutions include removing the DISTINCT operator from the query, asynchronously inserting search terms, and managing the number of tracked terms more efficiently. However, the problem continues. It's clear a broader review of Magento's structure and caching process is needed. In navigating this digital conundrum, it underlines the importance of continual learning, adaptation, and improvement to restore and enhance website performance.

Full article here: https://lawsuithelpdesk.com/unraveling-the-mystery-how-magento-2-3s-update-unleashed-a-cpu-load-crisis-the-pioneering-fixes-to-restore-your-sites-performance/

YouTube
LinkedIn
LinkedIn
Share