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

Question

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?

Tasadduq Burney · Answer

Answer to the core question
Shopware’s cache:warmup command operates on the cache.adapter.default service. It does not detect or warm a secondary adapter, so you cannot warm the filesystem and Redis pools in a single run.
What to do if you need both pools ready before traffic arrives

Run cache:warmup once with the filesystem adapter active (the default when Redis is not configured).
Then switch the default to Redis (e.g. by editing config/packages/cache.yaml or using a deployment hook) and run cache:warmup again.
Alternatively, write a small script that performs HTTP GET requests to the shop’s public URLs and stores the responses through the Redis client. This bypasses the need for real‑user traffic and keeps the filesystem cache untouched.

Detecting which adapter is active
There is no automatic event that informs the warm‑up process of the current adapter. You can check at runtime:
php bin/console debug:container cache.adapter.default

or inspect the container configuration. If the output shows cache.adapter.redis, Redis is the active HTTP cache; otherwise, the filesystem adapter is in use.
Verification after warm‑up

Confirm the adapter: php bin/console cache:pool:info cache.adapter.redis.
Check Redis keys (replace shopware: with your prefix): redis-cli keys 'shopware:*'. A non‑empty result indicates the cache was populated.
Make a request to a known page and inspect the X-Cache-Status or Surrogate-Control headers. A transition from MISS to HIT confirms the cache served the response.

Missing diagnostic detail
Could you tell me which Shopware major version you are running? The behavior of the HTTP cache system and the availability of a native Redis adapter can differ across releases.

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

1 answer

Answer to the core question

What to do if you need both pools ready before traffic arrives

Detecting which adapter is active

Verification after warm‑up

Missing diagnostic detail

Your perspective belongs here.

0 question comments