HOSTING TIPS ARCHIVE
Redis: hosting guides
Practical steps and checks for hosting, WordPress and performance. Browse a topic or use the dates to explore the experience behind the advice.
9 guides, newest work first.
Running Varnish in front of a Redis page cache, without stale pages
Varnish and a Redis page cache can make WordPress very fast together, but only if they purge as one. The VCL and purge rules that keep both caches honest.
Stock changes need their own cache invalidation
An order can change what a shop should display without anyone pressing Update on the product. I make the cache listen to those changes too.
Cron, wp-admin and the front end need to agree where temporary data lives
A site can have a persistent object cache and still repeat the same remote calls if some request types quietly keep transients only in memory.
Background cache refresh needs a budget too
Serving an older page briefly can keep a site responsive. Rebuilding everything at once can undo the benefit.
Move large cache clears into a background queue
Clear large caches in bounded batches, keep the admin request short and show whether the job has finished.
A shared Redis service needs boundaries for clearing as well as storing
I make a site’s cache clear stay inside that site. Prefixing writes is only half of the job.
Cache product data with its pricing context
I can reuse expensive product calculations, but only when the cache key describes the price the shopper is meant to see.
PHP in the browser and PHP in cron must agree on the cache
The same cache key is not enough. Every process that reads it has to understand the value written underneath it.
A slow cache should not hold the whole site hostage
I put a time budget around Redis so that a temporary cache problem does not quietly occupy every PHP worker.
No guides match those filters. Try another topic or reset the filters.