Dealing with Heavy Traffic: WordPress and Turbocharged
by David Peralty on May 2nd, 2007 
3 Comments
Over on the Turbocharged blog, there is a great, in detail post for semi-advanced to advanced WordPress users to help them deal with heavy traffic.
Everyone’s been there at least once. One of your blog pages gets dugg or slashdotted. What to do?
WordPress is often maligned as a resource-hungry blog platform — one that requires a lot of resources to run in high-traffic settings. But believe it or not, it’s possible to survive traffic spikes, while still serving pages to your audience swiftly. And you won’t need big iron to do it.
Throughout this guide, I’ll make a few assumptions on your part:
1. You’re using Apache to serve your pages, and you can change your Apache configuration.
2. You’re storing the contents of your blog in a MySQL database, the configuration of which you can change.
3. You’re running Turbocharged, or you have access to install WordPress plugins.If these don’t apply to you, don’t worry — we’ll explore (sadly, less effective) alternative approaches so you can still fend off traffic storms.
It is an interesting article to check out if you are interested in dealing with constant heavy traffic.
I like my article better. This doesn’t go into any detail!
Elliott.
I’ve caught you around the Web making these sorts of comments. Nah, I don’t blame you, but why, instead of pooh-poohing someone else’s free efforts, don’t you promote your own story without disparaging mine?
If you’re going to criticize someone else’s article, at least write a longer one yourself. Build the better mousetrap, and learn how to promote it. Don’t pout because I had a Diggstorm on it, I seized the opportunity to plug that article, and you didn’t do any of those things.
Oh yeah, for the record, I served the Spread this number traffic storm while simultaneously serving the Turbocharged article. All from the same server, linked by ./, TPB, Digg, Reddit and Del.icio.us.
And yes, it goes into detail.
Nice!