Skip to content
Lawsuit Help Desk

Lawsuit News Center

Decoding the Mystery: How Magento 2.3's Popular Search Term Cache is Straining Your Database and The Simple Fix You Need

Decoding the Mystery: How Magento 2.3’s Popular Search Term Cache is Straining Your Database and The Simple Fix You Need

Magento 2.3 has become a popular e-commerce solution, but a hidden computational issue may strain databases. The problem originates from a search term cache query which can cause high CPU usage and performance lag. This computationally expensive query, SELECT DISTINCT COUNT(*) FROM search_query WHERE (store_id = 1) AND (num_results > 0), specifically, can significantly slow down larger search_query tables and hinder user experience. A temporary solution removes the query's distinct operator, reducing run time from 10 to 2-3 seconds. This however does not fully address the issue as it does not tackle the num_results > 0 condition. This condition, though slowing the query, is crucial for the search term cache feature. A comprehensive solution that improves performance without compromising key features is still needed. The issue emphasizes the need for continuous observation and innovation in e-commerce.

Full article here: https://ipllfirm.com/all-insights/news-and-articles/decoding-the-mystery-how-magento-2-3s-popular-search-term-cache-is-straining-your-database-and-the-simple-fix-you-need/