WordPress errors a problem? Too high of a load for your web host? Worried about getting dugg, stumbled, or slashdotted? Learn now to “traffic proof” your WordPress site or blog!
This is installment #13 in 30 WordPress Hacks in 30 Days!
If you’ve blogging for any length of time, or if you own multiple blogs at one time or another you’re likely to have a problem with “too much traffic”. In this hacks series I’ve shown you how to keep your database maintained, but that doesn’t really matter if your starting to get 20,000 unique views per day or more. I’ve found over the that’s about the tipping point for most shared web hosts, the point at which your site reaches more than 250,000 “requests” per day or more and it starts maxing out the resources alloted to your domain. Every single time someone visits your WordPress site, it makes “calls” to the database server to retrieve the posts, and the pages, and the categories, and header, and the footer, and your archives, and on and on and on. Get the picture? One page load could mean a dozen+ “calls” to the database. That’s why 20,000 “page views” could mean “250,000 requests” for your site.
WP-Cache hasn’t been updated in a few years from what I saw on their web site, but that’s ok because “WP-Super Cache” has come along. It’s bigger and better than WP-Cache because the PHP engine is never called and it’s much quicker. Now, for those of you new to WordPress that might not be so technical – what is a “cache?” A cache is when you have common pages stored so they don’t have to be fetched from a database every time if nothing has been updated. Your web brower has a “cache” and it uses the copy of web pages on your PC if nothing has changed on the web version. The WordPress wp-super-cache plugin speeds up pages on your blog in the same way.
As always – if you have problems, questions, or something to add – please comment now!