Daniel Bachhuber

Chris Reynolds

Matthew Boynes

Pantheon Systems

John Spellman

Josh Koenig

<p><a href="https://circleci.com/gh/pantheon-systems/wp-redis/tree/master" rel="nofollow ugc"></a></p>
<p>For sites concerned with high traffic, speed for logged-in users, or dynamic pageloads, a high-speed and persistent object cache is a must. You also need something that can scale across multiple instances of your application, so using local file caches or APC are out.</p>
<p>Redis is a great answer, and one we bundle on the Pantheon platform. This is our plugin for integrating with the cache, but you can use it on any self-hosted WordPress site if you have Redis. Install from <a href="https://wordpress.org/plugins/wp-redis/" rel="ugc">WordPress.org</a> or <a href="https://github.com/pantheon-systems/wp-redis" rel="nofollow ugc">Github</a>.</p>
<p>It’s important to note that a persistent object cache isn’t a panacea – a page load with 2,000 Redis calls can be 2 full seconds of object cache transactions. Make sure you use the object cache wisely: keep to a sensible number of keys, don’t store a huge amount of data on each key, and avoid stampeding frontend writes and deletes.</p>
<p>Go forth and make awesome! And, once you’ve built something great, <a href="https://github.com/pantheon-systems/wp-redis/issues" rel="nofollow ugc">send us feature requests (or bug reports)</a>. Take a look at the wiki for <a href="https://github.com/pantheon-systems/wp-redis/wiki" rel="nofollow ugc">useful code snippets and other tips</a>.</p>
<h3>WP-CLI Commands</h3>
<p>This plugin implements a variety of <a href="https://wp-cli.org" rel="nofollow ugc">WP-CLI</a> commands. All commands are grouped into the <code>wp redis</code> namespace.</p>
<pre><code>$ wp help redis

NAME

  wp redis

SYNOPSIS

  wp redis <command>

SUBCOMMANDS

  cli         Launch redis-cli using Redis configuration for WordPress
  debug       Debug object cache hit / miss ratio for any page URL.
  enable      Enable WP Redis by creating the symlink for object-cache.php
  info        Provide details on the Redis connection.
</code></pre>
<p>Use <code>wp help redis <command></code> to learn more about each command.</p>
<h3>Contributing</h3>
<p>See <a href="https://github.com/pantheon-systems/wp-redis/blob/master/CONTRIBUTING.md" rel="nofollow ugc">CONTRIBUTING.md</a> for information on contributing.</p>


WP Redis

Awesome!!


        .+.
        .+?:
         .+??.
           ??? .
           +???.
      +?????????=.
      .???????????.
      .????????????.

     ########### ########
     ############.#######.
     ####### ####  .......
     ######## #### #######
     #########.####.######
     ######  ...          
     #######.??.##########
     #######~+??.#########
     ########.??..
     #########.??.#######.
     #########.+?? ######.
               .+?.
         .????????????.
           +??????????,
            .????++++++.
              ????.
              .???,
               .~??.
                 .??
                  .?,.


Do a little dance

Works like a charm and significantly improves the page rendering speed for my website. Play nice with https://wordpress.org/plugins/batcache/. These two allow me to get literally light speed performance for static pages.

Works like a charm!

Back your WP Object Cache with Redis, a high-performance in-memory storage backend.

adelong01

<p>QuantumCache accelerates WordPress by caching database query results and content fragments used to build pages. Instead of caching entire HTML pages, it reduces the database work required to render pages while preserving WordPress’s native invalidation behavior.</p>
<p>It is <em>not</em> an output buffer or page cache, and it does not replace existing page caching solutions.</p>
<h3>Features</h3>
<ul>
<li>Caches the results of the main front-end <code>WP_Query</code> for anonymous requests.</li>
<li>Tag-based invalidation: purge by post ID, post type, or taxonomy.</li>
<li>Fragment caching for <code>the_content</code> (classic) and core blocks such as <code>core/post-content</code>, <code>core/latest-posts</code>, <code>core/archives</code>, and <code>core/navigation</code>.</li>
<li>Multiple storage modes:
<ul>
<li>Auto – use Redis if available, otherwise fall back to MySQL.</li>
<li>Redis – fastest mode; uses the PHP Redis extension.</li>
<li>MySQL – portable fallback using compact tables (<code>qc_entries</code>, <code>qc_tagmap</code>).</li>
</ul>
</li>
<li>Compatible with the Redis Object Cache drop-in.</li>
<li>Avoids wp_options and postmeta storage – all cache data is stored in Redis or<br />
QuantumCache-owned database tables.</li>
<li>Multisite-aware: per-site prefixes and per-site tables.</li>
<li>WP-CLI commands: <code>wp quantumcache flush</code> and <code>wp quantumcache status</code>.</li>
<li>Metrics data layer: persistent hit, miss, store, and purge event counters available via <code>Metrics::totals()</code> and <code>Metrics::deltas()</code>.</li>
</ul>
<h3>Performance summary</h3>
<p>In benchmarks on a plugin-heavy WordPress site (WooCommerce + Yoast SEO),<br />
QuantumCache reduced per-request database queries by up to ~99% on cached pages<br />
and achieved cache hit rates exceeding 97% with Redis.</p>
<p>In the benchmark environment:</p>
<ul>
<li>Redis mode reduced warm TTFB by roughly <strong>23–27%</strong> and total response time by <strong>18–21%</strong> versus an uncached baseline.</li>
<li>MySQL fallback mode delivered <strong>modest improvements (~3–10%)</strong> when Redis was unavailable.</li>
</ul>
<p>Actual results depend on theme complexity, plugin load, database topology, and traffic patterns.</p>
<h3>When to use QuantumCache</h3>
<p>QuantumCache is useful when:</p>
<ul>
<li>Your site already uses a page cache (such as a CDN, reverse proxy, or caching plugin) but WordPress still performs significant database work.</li>
<li>You want faster response times without relying solely on full-page caching.</li>
<li>Your hosting environment supports Redis, or you want a portable MySQL fallback.</li>
</ul>
<p>QuantumCache complements page caching rather than replacing it.</p>
<h3>What QuantumCache does NOT do</h3>
<p>QuantumCache is not a page cache or full HTML cache.</p>
<p>It does not replace solutions such as:<br />
* CDN caching<br />
* reverse proxy caches<br />
* traditional WordPress page caching plugins</p>
<p>Instead, QuantumCache reduces the database work required to build pages, making those systems more effective.</p>
<h3>Debug headers (optional)</h3>
<p>Enable <em>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> QuantumCache <span aria-hidden="true" class="wp-exclude-emoji">→</span> Send X-QC debug headers</em> to view cache status in HTTP responses:<br />
* <code>X-QC-Main: HIT | MISS | STORE</code><br />
* <code>X-QC-Store: AUTO | redis | mysql</code><br />
* <code>X-QC-Hydrated:</code> number of posts loaded from cache</p>
<p>Append <code>?qc_nocache=1</code> to any URL to bypass caching for that request.</p>
<p>Debug headers are sent only when explicitly enabled in settings and contain no<br />
personal or user-specific data.</p>
<h3>WP-CLI commands</h3>
<p>QuantumCache provides the following WP-CLI commands:</p>
<p>wp quantumcache status<br />
Shows the active backend, storage mode, and lifetime cache counters.</p>
<p>wp quantumcache flush<br />
Clears all cache entries for the current site.</p>
<p>Use –yes to skip the confirmation prompt.</p>
<h3>QuantumCache Pro</h3>
<p>QuantumCache Pro extends the core engine with advanced caching capabilities for WooCommerce and logged-in users.</p>
<p>See: https://quantumcache.io</p>
<h3>Privacy</h3>
<p>QuantumCache does not collect, send, or log personal data.<br />
It stores cache entries in Redis or its own MySQL tables.<br />
Other plugins on your site may handle cookies or data independently.<br />
No remote requests are made, and no data is transmitted to external servers.</p>


QuantumCache

Speeds up WordPress by caching database queries and fragments for anonymous visitors using Redis or MySQL, without storing cache data in wp_options.

WP Redis vs QuantumCache