How to prepare for Boingboing and Digg?
In the last two weeks, I saw two of our servers being pounded to death because of Boingboing and just early today, Digg (You guys know who you are. *hehe*). On a shared hosting environment, this could be disastrous.
What could happen?
- Your site would crawl due to massive number of visitors in a short span of time.
- If you’re running on a database driven-site/blog like WordPress, mySQL might max out and crash.
- You’d ran out of bandwidth and get suspended by your web host.
What you need to do to prepare for this?
- Inform your web host *before*, NOT during or after you got dugg or slashdot. Remember that in a shared hosting environment, all other sites hosted on the same server will suffer the same fate.
- If you have WordPress, you may want to install the wp-cache plugin. It can greatly reduce server load.
- If you can, convert the page to HTML or static page so mySQL won’t choke and Apache can take the extra load or user connections.
- If you have lots of images or downloadables, host them elsewhere temporarily, like Flickr or PutFile, to reduce bandwidth consumption and file requests.
Lastly, prepare for some huge bills from your webhost afterwards. People usually think being dugg or slashdot could translate to more earnings. What they forgot to take into account that the bandwidth consumed in that short duration could practically put a hole in their pockets.