When I first started hosting my own sites, I had no idea what caching was or why it was important. Then I wrote a couple of popular blog posts, and my server crashed.
Fast forward a few years, and I’m running a few different websites on a few different servers. Some get a steady stream of traffic; others get a huge spike now and again when a post is picked up by Hacker News. In both cases, configuring your cache is a great way to keep things from failing.
I’m very happy to say that I’ve finally set up a hugely efficient front-end page cache for WordPress. It doesn’t use a plugin. It doesn’t require hacking core. And it serves my website in 3 ms. 1
Thanks to a clever configuration of Nginx and Redis, WordPress has achieved … ludicrous speed!
- Yes, you read that right. Three milliseconds. This is exclusive of the time it takes to perform a DNS lookup or actually deliver the page. But it is proof that the bottleneck is no longer the server itself. ↩