Razvan Stanga

Imagine a high traffic website that needs post views as an algorithm to display posts on the homepage. 
This website also uses <a href="https://wordpress.org/plugins/vcaching/" rel="ugc">Varnish Caching</a>. So we need an AJAX based post views counter. 
Now imagine a minimum 5000 concurrent users browsing the website, so we can’t use the default “AJAX in Plugins” as live updates on the backend using update_post_meta will be very painful for the backend.
So what can we do ?
What if all these post views counts will be done in memory using Redis ? 
Then we run a cornjob using WP-CLI to sync the post views count in Redis to the WordPress database.
Redis Post Views was born.

Redis Post Views

Highly optimized post views counter using Redis

adelong01

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.
It is not an output buffer or page cache, and it does not replace existing page caching solutions.
<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 
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>
In benchmarks on a plugin-heavy WordPress site (WooCommerce + Yoast SEO), 
QuantumCache reduced per-request database queries by up to ~99% on cached pages 
and achieved cache hit rates exceeding 97% with Redis.
In the benchmark environment:
<ul>
<li>Redis mode reduced warm TTFB by roughly 23–27% and total response time by 18–21% versus an uncached baseline.</li>
<li>MySQL fallback mode delivered modest improvements (~3–10%) when Redis was unavailable.</li>
</ul>
Actual results depend on theme complexity, plugin load, database topology, and traffic patterns.
<h3>When to use QuantumCache</h3>
QuantumCache is useful when:
<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>
QuantumCache complements page caching rather than replacing it.
<h3>What QuantumCache does NOT do</h3>
QuantumCache is not a page cache or full HTML cache.
It does not replace solutions such as: 
* CDN caching 
* reverse proxy caches 
* traditional WordPress page caching plugins
Instead, QuantumCache reduces the database work required to build pages, making those systems more effective.
<h3>Debug headers (optional)</h3>
Enable Settings → QuantumCache → Send X-QC debug headers to view cache status in HTTP responses: 
* <code>X-QC-Main: HIT | MISS | STORE</code> 
* <code>X-QC-Store: AUTO | redis | mysql</code> 
* <code>X-QC-Hydrated:</code> number of posts loaded from cache
Append <code>?qc_nocache=1</code> to any URL to bypass caching for that request.
Debug headers are sent only when explicitly enabled in settings and contain no 
personal or user-specific data.
<h3>WP-CLI commands</h3>
QuantumCache provides the following WP-CLI commands:
wp quantumcache status 
Shows the active backend, storage mode, and lifetime cache counters.
wp quantumcache flush 
Clears all cache entries for the current site.
Use –yes to skip the confirmation prompt.
<h3>QuantumCache Pro</h3>
QuantumCache Pro extends the core engine with advanced caching capabilities for WooCommerce and logged-in users.
See: https://quantumcache.io
<h3>Privacy</h3>
QuantumCache does not collect, send, or log personal data. 
It stores cache entries in Redis or its own MySQL tables. 
Other plugins on your site may handle cookies or data independently. 
No remote requests are made, and no data is transmitted to external servers.

QuantumCache

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

Redis Post Views vs QuantumCache