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.

TMM Technology

<p>Visits website pages to warm (create) the cache if you have any caching solutions configured.</p>
<h3>Settings</h3>
<ul>
<li>Configure cache warming entry points and the depth of the warming;</li>
<li>Add all public site posts as entry points;</li>
<li>Add entry point sites sitemaps as entry points;</li>
<li>Select which types of assets to load, with 4 checkboxes: scripts, styles, images, fonts;</li>
<li>Set custom URL params (?foo=bar);</li>
<li>Set custom user agent;</li>
<li>Set custom request headers;</li>
<li>Set custom cookies;</li>
<li>Set connection timeout;</li>
<li>Set speed limit (pages to visit per minute);</li>
<li>Autorun Interval: to run the warming each N minutes;</li>
<li>Exclude pages (by substring or regex);</li>
<li>Rewrite URLs to HTTPS;</li>
<li>Visit pages second time without custom URL params (if they are set);</li>
<li>Warm-up posts (on their publication and edit (Can be seen in Logs -> Triggered)):
<ul>
<li>Set custom posts warming interval.</li>
</ul>
</li>
<li>Use object cache for tree storage, when it’s available.</li>
</ul>
<h3>Additional</h3>
<ul>
<li>Adds a graph to your dashboard with page load time before and after the warming (2 lines) per day.</li>
<li>Cleans up Action Scheduler log after itself (older than 30 days for failed actions, and older than 2 days for completed actions).</li>
</ul>
<h3>External services</h3>
<ul>
<li>Connect to paid service for warming from external global servers.</li>
</ul>
<h3>Run from code</h3>
<ul>
<li>Start: <code>\Cache_Warmer\AJAX::start_warm_up( false );</code></li>
<li>Stop: <code>\Cache_Warmer\AJAX::stop_warm_up( false );</code></li>
</ul>
<h3>Run from WP CLI</h3>
<ul>
<li>Start: <code>wp cache-warmer start</code></li>
<li>Stop: <code>wp cache-warmer stop</code></li>
</ul>
<h3>Required PHP extensions</h3>
<ul>
<li>json</li>
<li>simplexml (optional)</li>
</ul>
<h3>Bug reports / Questions / Suggestions</h3>
<p><a href="mailto:wp@tmm.ventures" rel="nofollow ugc">wp@tmm.ventures</a></p>


Cache Warmer


Developer is helpful and responsive.If you have a sitemap, click the option for this, set depth to 1, decide your update interval (match it to the default cache expiration time) and you're good to go.I use this alongside NGINX page caching and Redis object caching.


Does the job!

Visits website pages to warm (create) the cache if you have any caching solutions configured.

QuantumCache vs Cache Warmer