There is nothing about this that is not amazing.
"…halfway through the film, the Ghostbusters realize that NYNEX isn't a phone system at all: it's the embedded nervous system of an angel – a fallen angel – and all those phone calls and dial-up modems in college dorm rooms and public pay phones are actually connected into the fiber-optic anatomy of a vast, ethereal organism that preceded the architectural build-up of Manhattan. Manhattan came afterwards, that is: NYNEX was here first." There is no way this wouldn't be awesome. And: a great write-up from Geoff.
How to compile APC into the Marc Liyanage PHP5 package (which is clearly the most sensible one to be using on OSX). Though this is for Server, it works fine on desktop, and as such comes recommended.
"This toaster was built from scratch by Thomas Thwaites, a design student at the Royal College of Art, London, as a project in extreme self-sufficiency and to highlight the effects of mass production we take for granted." And this is what it looks like.
"I'm Thomas Thwaites and I'm trying to build a toaster, from scratch – beginning by mining the raw materials and ending with a product that Argos sells for only £3.99. A toaster." This is clearly amazing, and a timely reminder of, you know, what the age of mass production really means.
Your guide to surviving the Digg avalanche with WordPress
26 November 2008
My recent talk about what might happen if gamers ran the world made Digg yesterday, and went a bit big. Big to the point that I got a nice email from my host pointing out that my PHP processes were killing the entire shared host that I’m hosted on, and that I needed to rectify this immediately.
The fires were mainly calmed by installing WP-Super-Cache, which did pretty much what it says on the tin. That said, I did learn a few things from the incident. In no particular order:
- WordPress’ PHP processes for rendering a page are really, really intensive. Most of the time, that’s not a problem, but when you’re being bombarded with hits, it’ll take it’s told. Flat HTML might be the way forward.
- Super-Cache isn’t exactly difficult to install, but it requires permissions in lots of places. The best advice I can give is to walk through the installation instructions carefully, and when it doesn’t work, go over the troubleshooting guide in
readme.txtone step at a time. The few issues I had were resolved by walking through the troubleshooting process.
- Most importantly, a combination of the two parts above: you should assume that at some point, you’re going to need this kind of caching, and you’re going to need it fast. Installing and configuring WordPress plugins on a server being bombarded with hits really isn’t much fun. Instead, install the caching plugin of your choice when you set your server up, and make sure it’s working at that time. Then, when the horde descends upon your lowly shared host, you can head straight there and click “enable caching”, rather than having to fight fires for an hour when you really should be working, or in the pub. This also means you can configure the thing to not cache your feed, which is a useful thing to be able to do; I’m about to head off and do that now.
Everything appears to have cooled off now, and I’m not getting any more emails from Joyent about my usage. To Joyent’s credit, they were helpful at explaining the problem and tolerant of the time it took for me to fix things, which was appreciated. And next time I get an absurd amount of traffic, with any luck, I’ll be ready for it.