HOSTING TIPS ARCHIVE
Performance: 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.
21 guides, newest work first.
PHP 8.6 for WordPress: compatibility checks
What I check before moving WordPress to PHP 8.6: plugin and extension compatibility, Redis formats, OPcache memory, background jobs and a tested rollback.
PHP 8.6: new features and upgrade guide
PHP 8.6 new features explained: Duration, clamp, callbacks and polling, plus compatibility, support dates and practical checks before upgrading.
Splitting work across uneven machines: claims, big chunks first, and a duplicate tail
Distributing browser renders across uneven machines: current claims, strict chunk IDs, largest-first scheduling and a duplicated tail.
Managing a news aggregator's sources without slowing the site down
A publisher directory that took 174 MB, a cache stampede, adding outlets with a way back and retiring stale stories without deleting them.
Give every Redis key a lifetime, even when the code asks for a week
Ace Redis Cache now caps every object cache lifetime so cold keys stop crowding shared Redis, and why values over 64 KB were never being stored.
Cache the page, not the reader: a Redis page cache on a busy news site
Nothing per-reader in cached HTML, time windows in cache keys, and a newsroom-aware most popular list that stays live inside a cached page.
AI vs the Exponential Time Hypothesis
OpenAI claims ETH is false. What was checked, why encryption is safe, and what I measured in my own code.
Invalidate a Redis cache without scanning it
Clearing 100,000 Redis keys took 2.4 s with SCAN and DEL, 0.26 s with batched UNLINK and one command with a generation counter. Code and trade-offs.
When a benchmark win vanishes in production
A 3,000 times faster pre-check gave wrong answers on real data until it modelled the map edge. Model boundaries, check correctness and measure real inputs.
Get more from Cloudflare without making WordPress fragile
A practical Cloudflare setup for WordPress: cache boundaries, Turnstile, analytics, Varnish, Redis and honest measurements from TalkFuse and Sheffield Events.
Serve photography galleries without heavy downloads
Keep photographs clear while reducing unnecessary downloads, with sensible image sizes, loading priorities and a recoverable publishing process.
Keep a Raspberry Pi development server responsive
Check power, cooling, storage, memory and background concurrency so a Raspberry Pi remains useful during real development work.
Diagnose Linux bottlenecks before changing settings
Use a small repeatable baseline to distinguish CPU work, memory pressure, storage waits and application queues before tuning a Linux web server.
Check hosting and tracking before rewriting falling content
Work out whether falling traffic points to a content problem, a broken page or missing measurement before you change your articles.
Check EC2 CPU credits and storage limits before resizing
Investigate burstable CPU capacity and both sides of the EBS connection, then change the resource that actually constrains the workload.
zram swap on a web server: setup, numbers and rollback
Swapping to a cloud disk can make MySQL and Redis wait hundreds of microseconds per page. zram swaps to compressed RAM instead. Setup, real numbers and rollback.
Caching a WordPress block means keeping more than its HTML
A block can register scripts, styles and interactive state while it renders. I need those effects back on a cache hit too.
Apache tuning and hardening: PHP-FPM, HTTP/2, caching and Cloudflare IPs
Practical Apache tips: switch to the event MPM with PHP-FPM, turn on HTTP/2 and Brotli, cache static files properly, read real visitor IPs behind Cloudflare and hide what should be private.
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.
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.
Check the Apache configuration that is actually loaded
Before changing an Apache limit, I trace the running service to the configuration it reads. A plausible file in the right directory can still be inactive.
No guides match those filters. Try another topic or reset the filters.