Yesterday my photography blog got “farked“. This ought to have been a day for celebrating but in actual fact the first I knew about it was when someone emailed to say my site was down.
It turns out my web host has a policy where they disable a site that uses more than 20% of processor. It seems that my (pretty much default other than template) Drupal install was gobbling up resources. According to Metrics I received an additional ~8000 visitors before my blog died (or was killed, either or).
Lessons learned
- Use traffic management settings before things like this happen – in Drupal that means switch caching and throttling on and be careful what frivolous modules you have running
- Check your blog every day at least, don’t wait for a visitor to tell you that your blog is down
- You get what you pay for where hosting companies are concerned
- Read the terms and conditions before signing up
- Take regular backups of all important files and databases
- Host critical domains outside of your hosting agreement (if things get nasty you don’t want your domain held to ransom)
- It might be a hobby blog to you but people miss your stuff when it isn’t there
Luckily my photography blog is a labour of love rather than something I rely on for income. Just imagine if it was critical and I had been away on business or vacation, I might have been looking at a hole in my bank balance a week from now.
The thing that will be most interest to you guys that have been following the social bookmarking threads is out of those ~8000 additional visitors I gained one new user, 10 additional adsense clicks and zero RSS subscribers.
Just goes to show, I would much rather receive steady traffic than a flood!
Added: A couple of Metrics charts to see a little better what happened. Notice the cut-off of traffic when my blog was pulled!
Added: 23rd August, the party is over. Fun while it lasted!