I recently read a post on Coding Horror where Jeff Atwood was crowing about how well the blogging platform Moveable Type has worked for him over the last years. I’ve been a WordPress user ever since I started blogging, and hadn’t realized that in a default installation, the dynamic page creation WordPress uses can really limit the number of pages that you can serve at a time. And although I have yet to write that breakthrough post that gets on Digg, Reddit, and Slashdot all at the same time, I figured it might still be prudent to take steps to minimize the load on my relatively puny server.
After clicking through and reading some of the links describing different caching schemes for WordPress, I decided to grab one of the highly-rated plugins to handle caching this blog. I chose WP-SuperCache. Although it has a bewildering variety of options, it boils down to taking the dynamically-generated pages you publish, boiling them down to the raw HTML that ends up served to the client, and caching that on the server.
When this is done, the webserver only has to sling raw HTML to the browser, rather than make multiple round-trips through PHP to the MySQL database to construct the page. This should be both faster and lower load on the server.
So feel free to load up this site as much as you want, and send links to all your friends. Sure, even include another few hundred “Anubis Gates” spammers. I can take it!
I hope to eventually have some more programming-related updates here; I’m working on a solution at work to add compile-time type-safety to Windows message passing that will make a good article (or two) when I’m done.