I released WP Super Cache 0.5.3 on Friday last. From the stats it looks like people are upgrading which is good news!
This version has a number of fixes and improvements:
- If your blog is installed in a sub-directory you’ll want to upgrade. This version fixes the mod_rewrite rules that search for the cached files. If upgrading, make sure you delete the Super Cache rules so they’ll be upgraded. (Thanks Otto42)
- With a click of a link in the backend page you can view your mod_rewrite rules to check that they are ok. This may help the adventurous who want to upgrade those rules manually too.
- The plugin now warns if your blog’s root directory is writeable. Most of the time there’s absolutely no reason for this so it’s good to be reminded to fix it.
- Check that $mutex is set. This is really only useful if your server is borked and the filesystem is mounted read-only but it’s good to be complete.
Wondering about the title? Check out this traffic graph Scott Beale posted a few weeks ago and you’ll understand. One of his posts hit the front page of Digg (twice) then Slashdot.org, and was covered by lots of other blogs and media. Wow.
On December 12th our blog hit a record high of 222,523 views in one day.
13 thoughts on “Phoar! What a spike!”
Wow – that’s a heck of a traffic spike! Here’s hoping he gets some additional readers from it!
Will the $mutex fix check for old locks (can that even be done efficiently?) I got nailed by a hung mutex lock on a wp-cache file, which slowly locked up web processes waiting for the lock to clear, eventually shoving me into my max virtual proc limit – suddenly my sites are returning 500 Errors!
Definitely think it’s time to make the switch regardless – your new cache plugin looks great.
It won’t clear out old locks, but I guess one way of doing that is by checking the age of an existing lock and deleting it when it’s over X minutes old.
That’s definitely an impressive spike …
HOLY CRAP! Look at that spike! I hope you don’t get charged a massive overage from your webhost! I’ve been lucky enough to get .. 30 .. as my top. Probably has something to do with I don’t have any service or anything the public really needs to see 😀
Keep up to good work!
I found a small(ish) bug with this verison’s detection of a writable blog directory. If your runnign php as a cgi, or have it setup through suPHP (as many webhosts do), your directory by default will be writable. not because it’s writable to the webserver, but because it’s writable to the php script which runs as the user.
WOW! Congratulations. That beats the crap out my best day (or month) *coughs.
Looking at that spike, I sure hope he had his own plugin running at the time! 😀
Wow, that’s a true test of server resiliency. Very impressive.
Ok, that graph really piqued my interest. That’s a serious spike! You talked me into it….I’m going to install WP Super Cache right now!
if that was my server it would have been a smoldering pile of scrap metal by now 😉
if dat were me Id be a nigger ya’all
Here’s an interesting bug.
If you have a blog post with multiple pages, and someone posts a comment… only 1 page expires not both.
I’ve also noticed that even when logged in, the site doesn’t always recognize you as logged in when supercache is enabled. But that’s minor.
WWooo.. This is kind o a spike.. that Digg or what so ever Social Media site could.. do.. this what you called.. A golden Information Mine spike.