The Magento 2.3 upgrade caused unexpected increases in database CPU load. The problem was traced back to a performance glitch in the search term cache that led to CPU usage spikes and slower response times across various Magento versions, negatively affecting user experience. A regular, resource-demanding query counting distinct search terms with positive results was identified as the cause. As the search term table grows, the issue worsens, resulting in longer execution times and increasing CPU load. The Magento community suggested fixes like removing a specific condition or overriding a function, but the problem persists, underlining the need for an effective solution. It highlights the challenges in managing database operations, cache and query performance, and the importance of continuous learning and collaboration in today's digital commerce domain.
Full article here: https://lawsuithelpdesk.com/unraveling-the-mystery-how-the-magento-2-3-upgrade-unleashed-a-database-cpu-load-nightmare-and-the-quest-for-a-fix/