Magento 2 Cache Overload Fix
Budget: $30 – $250 USD
My Magento 2 store is generating cache files at an aggressive rate and, even though I flush the cache every day, CPU load and inode counts still spike until the site slows to a crawl. I need someone who can step in, pinpoint why the cache is ballooning, and implement a sustainable fix that brings CPU usage and inode consumption back to normal levels.
You’ll start by auditing the current cache configuration (file/Redis/Varnish settings, cron jobs, third-party modules) and reviewing server logs to spot runaway processes or extensions. From there, the goal is to:
• Stop unnecessary cache writes and trim existing cache size without breaking storefront or admin performance.
• Tune Magento’s cache, session, and indexer settings so daily manual flushes are no longer required.
• Optimise server-side parameters (PHP-FPM, MySQL) to keep CPU usage stable.
• Deliver clear notes on changes made so I can maintain the setup going forward.
Success is simple to measure: after your work the cache directory remains under control for at least a full day’s traffic burst, the site’s CPU load averages within normal limits, and inode count no longer hits the host cap.
If you’ve solved similar Magento 2 cache explosions before, I’m ready to get started.
You’ll start by auditing the current cache configuration (file/Redis/Varnish settings, cron jobs, third-party modules) and reviewing server logs to spot runaway processes or extensions. From there, the goal is to:
• Stop unnecessary cache writes and trim existing cache size without breaking storefront or admin performance.
• Tune Magento’s cache, session, and indexer settings so daily manual flushes are no longer required.
• Optimise server-side parameters (PHP-FPM, MySQL) to keep CPU usage stable.
• Deliver clear notes on changes made so I can maintain the setup going forward.
Success is simple to measure: after your work the cache directory remains under control for at least a full day’s traffic burst, the site’s CPU load averages within normal limits, and inode count no longer hits the host cap.
If you’ve solved similar Magento 2 cache explosions before, I’m ready to get started.