Skip to content
Lawsuit Help Desk

Lawsuit News Center

Title: Unraveling the Impact of Magento 2.3's Popular Search Term Cache: An In-depth Analysis of Performance Glitches and Potential Fixes.

Title: Unraveling the Impact of Magento 2.3’s Popular Search Term Cache: An In-depth Analysis of Performance Glitches and Potential Fixes.

The Popular Search Term Cache, introduced in Magento 2.3.0, initially sparked enthusiasm for its potential to enhance user experience. Nevertheless, it led to performance issues, including increased database CPU load, due to a problematic query related to popular search terms, specifically the num_results > 0 clause. This issue persisted even when search suggestions were disabled and ElasticSearch enabled. The problematic query was identified as SELECT DISTINCT COUNT(*) FROM search_query AS main_table WHERE (main_table.store_id = 1) AND (num_results > 0). Removing the superfluous DISTINCT operator drastically reduced query time from 700ms to 2ms, significantly enhancing performance. However, balancing site performance with the integrity of search results became a new challenge. Proposed solutions include overriding the execute function and inserting search terms in batches asynchronously, though they require careful consideration to maintain original functionality and user experience.

Full article here: https://medium.com/@lawsuithelpdesk/unraveling-the-impact-of-magento-2-3s-04406f8c7966