The thing about WordPress CMS that don’t many people know is its ‘bloatedness’. That’s why I run only the basic plugins and options using WordPress, for previously I’ve been warned by my host that the server load was extremely highly

Aside from running WordPress on a ‘light’ mode, I also uses cache methods where pages are served in cache to reduce server loads. WP Cache by Ricardo Galli Granada served me well these few years so far but until a few weeks back that is

One of my entry got Digg and there was a surge of huge traffic and my server couldn’t really handle it. My host pulled the plug off the website and I lost countless advertising revenue from that one particular traffic. I wasn’t prepared

Well to prevent future ‘mishap’, I’ve been doing more reading up and I’m sure you have stumbled upon WP Super Cache by Donncha O Caoimh like I do. It is based on WP-Cache but with ‘improved’ features like

• Automatically disable gzip compression in WordPress instead of dying
• A “lock down” button. I like to think of this as my “Digg Proof” button. This basically prepares your site for a heavy digging or slashdotting. It locks down the static cache files and doesn’t delete them when a new comment is made.
• Automatic updating of your .htaccess file
• Better version checking of wp-cache-config.php and advanced-cache.php in case you’re using an old one.
• Better support for Microsoft Windows.
• Properly serve cached static files on Red Hat/Cent OS systems or others that have an entry for gzip in /etc/mime.types

Well just what I was looking for in the Digg Proof feature. I do hope future Digg traffic will not result in my server crashing and revenue lost.

This preparation recently by me, hours in front of the computer going through all my blog in the ‘upgrade’ is worth it

Are you using cache plugin yourself? If not, well you should. Don’t say I never told you