Choosing Between Filesystem and Redis HTTP Cache Adapters for Reliable Warm‑up in Shopware

Goal: Ensure that Shopware’s HTTP cache is fully populated before production traffic arrives, regardless of whether the filesystem or Redis adapter is used.

Constraint: The default warm‑up mechanism only populates the filesystem cache; when the Redis adapter is enabled the cache remains cold until the first request, which can cause latency spikes. Additionally, a silent fallback to the filesystem adapter can occur if the Redis connection is misconfigured, making it difficult to verify which adapter is actually active.

Uncertainty: It is unclear whether the warm‑up process can be made adapter‑agnostic or if a separate procedure is required to pre‑load the Redis cache without relying on real‑user hits.

Questions:

• Can the warm‑up feature be configured to warm both the filesystem and Redis HTTP cache pools simultaneously?
• If not, what is the recommended method to pre‑populate the Redis cache in a production‑safe way?
• Are there configuration options or events that allow the warm‑up process to detect the active adapter and act accordingly?