How I saved Magento 2 with 1 million products and 10 million CMS pages from 504 errors

▤ Summary

This article walks through how to stabilize a very large Magento 2 store that was hitting 504 errors under crawler load. It focuses on cache architecture, including Redis, Varnish, browser caching, and Full Page Cache design, to reduce pressure on PHP-FPM and MariaDB. The author shows how to separate cache layers, tune TTLs, and use Varnish correctly to keep the working set in memory or file-backed storage. It also covers Magento-specific settings such as cacheable blocks, ESI, and disabling unnecessary dynamic rendering for better performance. The main takeaway is that careful cache layering and crawl-aware tuning can dramatically improve uptime and response times for large Adobe Commerce deployments.

▦ Linked Companies