For those who don't know (every time I mention this, I get like 10 upvotes. Apparently a lot of people even on HN don't know about it!), if you want to get a (Google) cached version of a page, just type 'cache:[URL]' in Google search bar and press return.

'cache:http://joelrunyon.com/two3/an-unexpected-ass-kicking -> http://webcache.googleusercontent.com/search?hl=en&outpu...

Thanks sir! And never underestimate the value of the little cantrips like that to somebody who isn't aware of them. I was astounded that most people didn't know CTRL+F, and I always ask people if they know about it.(http://www.theatlantic.com/technology/archive/2011/08/crazy-...)

Does Google document these all anywhere? I could've sworn they used to have a page listing them, but I can't find it anymore. There are a few third-party listings, though, e.g. this one from SEOmoz: http://www.seomoz.org/article/the-professionals-guide-to-adv...

Haha! 14 points already... Told you!

It's slow, but we should have the server back up and running.

Sorry about this. Didn't think the site was going to get hammered like it did.

Your site took an unexpected ass-kicking.

50,000 hits in a few hours will do that to a site. Time to upgrade.

Depends. 50k hits in 3 hours is 5 hits a second. I could serve more than 10 hits a second on the first web server I ever set up, in 1994, on an SGI Indigo 2 with maybe a 250MHz CPU and 256 megabytes of RAM, using NCSA httpd, which spawned a new process for every hit. Under IRIX. While I was using it as a workstation. Also, doing a reverse DNS lookup for every hit for the access log.

My current home page, http://canonical.org/~kragen/, benchmarks at 4000 requests per second with ab on localhost. That's roughly a thousand times the load you were under. This is not because our server is a thousand times faster than yours. (It's a dual-core 2.4GHz Celeron, running Apache.) This is because your server is doing a thousand times as much work as it needs to in order to serve that page.

I'm asserting that your server isn't a thousand times slower because a thousand times slower would be a high-end eight-bit microcontroller. An Arduino, say. Feel free to correct me if your server is in fact running on an Arduino or equivalent.

I've had my tech guy speed things up. Got off shared hosting, on a VPS and should have things sped up all around. Still need to cut all the javascript in the current theme, but that's another project for another day.

The JS might actually speed things up by allowing you to do stuff on the client that you'd otherwise have to do on the server.

with an out-of-the-box configuration, Wordpress is notorious for dying if you so much as breathe on it. It requires generous lashings of caching to make it workable.

If you haven't already, install W3 Total Cache or WP-Supercache.

W3 TC is installed. Just had a massive influx over the last two days that overwhelmed even that. Seems like its time to upgrade hosting plans.