Which cache backend makes sense for Doctrine ORM on a low-traffic PHP app: APCu or Redis?

Question

I'm running a small, low-traffic PHP application on Doctrine ORM (2.x/3.x line) and want to cut database and CPU costs. I've already set associations to lazy fetch and pre-generated proxies with auto_generate_proxy_classes disabled in production, which removed most of the obvious overhead.

The remaining decision is the metadata and query cache backend. The documentation supports adapters such as APCu and Redis, but the trade-offs for a tiny workload aren't clear to me. APCu is per-process, so with several PHP-FPM workers each worker keeps its own cache, affecting hit rates and invalidation. Redis is shared and consistent across workers, but adds an extra service to deploy, secure, and monitor — which itself has a cost that may exceed what a low-traffic app saves.

I also want to avoid making things worse: I've read that lazy loading can produce N+1 query patterns if associations are touched inside loops, so I plan to verify query counts with the SQL logger in staging before and after any change.

For a workload with only a handful of requests per minute:

Is a shared Redis cache measurably better than per-process APCu at this scale, or is the operational overhead rarely justified?
Which cache (query, result, metadata) gives the biggest cost reduction for infrequent requests?
What metric best confirms the choice — cache hit rate, query count per request, or response time?

Tasadduq Burney · Answer

Answer
For a low‑traffic Doctrine ORM application (a handful of requests per minute) APCu is the appropriate cache backend; adding Redis rarely yields a measurable benefit and introduces operational overhead.
Confirmed facts

Doctrine’s metadata cache eliminates the need to parse class metadata on every request and provides the largest reduction in database load.
The query cache helps only when the same DQL statement repeats frequently; with few requests the gain is marginal.
Result caching is useful only if the same entity query runs many times within a single request, which is uncommon in a lightly used app.
APCu caches are per‑PHP‑FPM worker, but with a small, static metadata set the hit rate stays high even across workers.
Redis only adds value when you have many workers, need centralized invalidation, or share cached data across multiple app instances.

Likely explanation
Because the metadata set is tiny and rarely changes, each worker’s APCu cache warms up after the first few requests and then serves nearly all subsequent metadata look‑ups from memory. The per‑worker duplication does not significantly lower the overall hit rate at low request volume, while Redis would add latency from network round‑trips and require extra monitoring, security patches, and memory management.
Steps to enable and verify APCu

Install and enable the APCu extension (e.g., sudo apt-get install php-apcu or via PECL).
Ensure apc.shm_size is large enough for Doctrine’s metadata (e.g., 64M).
Configure Doctrine to use APCuCache for metadata and query caching:
$config->setMetadataCacheImpl(new \Doctrine\Common\Cache\ApcuCache());
$config->setQueryCacheImpl(new \Doctrine\Common\Cache\ApcuCache());

Leave the result cache disabled unless you profile and find repeated identical queries inside a request.
In a staging environment, enable Doctrine’s SQL logger and record the total number of SQL queries and average response time for a representative batch of requests (e.g., 100 requests) before enabling the cache.
After the cache has warmed up (a few requests), repeat the measurement.
Check APCu hit rate: apc_cache_info('user')['hit_rate']; a sustained rate above 90 % confirms the cache is effective.
If the query count drops by a noticeable amount (e.g., >20 %) and response time improves, the cache is delivering the expected benefit.

Missing diagnostic detail
If you run many PHP‑FPM workers (e.g., >20) and notice low APCu hit rates or frequent cache misses after code changes, let me know the worker count; that could shift the recommendation toward a shared Redis cache.

Which cache backend makes sense for Doctrine ORM on a low-traffic PHP app: APCu or Redis?

1 answer

Answer

Confirmed facts

Likely explanation

Steps to enable and verify APCu

Missing diagnostic detail

Your perspective belongs here.

0 question comments