You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bit late but i stumbled across this issue. The DB-Cache relies on transients that are cached. AFAIK transients will automatically be cached in memcache(d) or redis.
I made a test on our server: without memcache, transients are generated and viewable in the DB. With memcache enabled, no transients found in the DB but the output is cached (visible in the footer notice).
That's correct, the "DB" backend actually utilizes set_transient() which might end up in DB or an external object cache depending on the system setup.
Explicit memcached (since 2.0.7, 2013) has a slightly different structure, so it can be included directly in the webserver config to skip all WP logic and the same holds for the recently added Redis backend (which will be included in 2.4.0)
Both could be refactored to utilize WP's object cache abstraction and we should probably extend the documentation on the "DB" backend, but neither should have significant impact on the overall functionality.
Memcache (or Memcache_d_) and Redis support would be nice via
object-cache.php
.I think Simple Cache does this nicely. WP Spider Cache has a nice abstraction, too.
The text was updated successfully, but these errors were encountered: