fbpx
Decoding Magento's CPU Load Crisis: The Silent Culprit in Your Search Term Cache and How to Fix it

Decoding Magento’s CPU Load Crisis: The Silent Culprit in Your Search Term Cache and How to Fix it

"Decoding Magento's CPU Load Crisis: The Silent Culprit in Your Search Term Cache and How to Fix it

In the world of E-commerce, Magento has established itself as a formidable player, but with recent updates, it's experiencing some glitches that are not just pesky but slow down businesses significantly. This article dives deep into Magento's "CPU Load Crisis," pinpointing the problem to the frequent and time-consuming queries related to the popular search term cache causing an unexpected surge in the database CPU load. We will explore the cause, trace the issues, and most importantly, discuss plausible solutions to rectify this critical problem.

Unveiling the Hidden Crisis in Magento 2.3.4: The CPU Load Glitch

The hidden crisis tormenting Magento 2.3.4 users is the sudden spike in database CPU load. This performance issue cloaked in shadows roots itself in an unanticipated culprit: a frequent and time-consuming search query. The problem exacerbates with increasing search_query table size, which inevitably happens as a website's traffic and searches accrue. On a live site with 2.7 million search terms, the query duration can be as torturing as 23 seconds. Upgrading to Magento 2.3, expected to boost e-commerce businesses, ironically, triggered this crisis.

The Devil in the Detail: An Analytical Look at the Troublesome Query

The troublemaker is an application query: SELECT DISTINCT COUNT(*) FROM search_query AS main_table WHERE (main_table.store_id = 1) AND (num_results > 0). This query, as simple as it may appear, is the devil in the detail that is causing this performance issue. The query is performing a distinct count on the search_query table where the store_id is equal to 1 and where more than one search result exists. The larger the search_query table, the longer the query takes to complete.

Empirical Evidence: Reproducing the Issue in Different Magento Versions

This issue isn't unique to Magento 2.3.4, but it's also confirmed and reproduced in the latest 2.4.x branch of Magento, Magento 2.4.1-p1, Magento 2.4.5-p4, Magento 2.4.4-p1, and Magento 2.4.2-p2. The widespread prevalence indicates that this problem is a systemic flaw requiring an immediate solution.

Proposed Remedies: Removing the Redundant DISTINCT Operator and Other Solutions

Our data indicates that the DISTINCT operator in the search query is not required due to a unique constraint already present on query_text and store_id. As a result, one proposed solution is simple – remove the DISTINCT operator from the queries within \Magento\Search\Model\ResourceModel\Query\Collection to streamline computation and significantly improve query performance.

Shortcomings and Challenges: Potential Drawbacks of Existing Solutions

While removing the DISTINCT operator is a plausible solution, each remedy inevitably comes with its own set of potential drawbacks. For example, adding more columns to the select query might increase the workload for MySQL without necessarily improving performance. These changes aren’t merely code adjustments but also fundamental changes to how Magento's search function operates.

Looking Forward: Future-Proofing Magento’s Search Functionality for Optimal Performance

While Magento's current CPU load crisis presents a challenge, it also offers an opportunity – an opportunity to re-evaluate, refine, and perhaps even reinvent the platform’s search functionality. With thoughtful analysis, strategic changes, and comprehensive testing, a more robust, efficient, and future-proof Magento can emerge.

In the future, developers should consider stress testing scenarios that mimic real-world usage patterns. Magento could also benefit from fostering a proactive community engagement strategy, encouraging users to report bugs and performance issues.

Although these solutions have potential setbacks and need extensive evaluation and testing before implementation, it’s crucial to navigate through this CPU load crisis and turn it into an opportunity for improvement. We envision a future where Magento emerges as a more robust, efficient, and future-proof e-commerce platform by addressing these issues head-on and implementing changes that refine its search functionality, ensuring a more reliable, performance-oriented Magento."

YouTube
LinkedIn
LinkedIn
Share