Fooblog2000
Wednesday, March 21, 2007
I seem to have failed to note to everyone perusing this site for its foobar-ness that all foobar related posts have now been moved to my new site, Fooblog2000. I'll no longer be posting updates to my configurations here, which are now up to version 0.6 with some very nice new features such as ratings panels and a singles SCPL mode.
With that said, the interim period for the site, i.e. its opening month, has come to an end with quite a razzle dazzle; v0.6 of my configuration made it to the front page of Digg and fooblog consequently succumbed to the effects of lots of visitors. Fooblog uses Dreamhost as its provider which offers 2Tb of bandwidth a month; I had plenty of preparation for such an attack, or at least I thought I did. What I was not prepared for was a catastrophic failure of Wordpress 2.1.2. To save the MySQL databases from too much stress I turned on the advanced WP caching system, however when 2000 people arrived in an hour or so something went wrong and all WP pages failed to load. Due to the stresses of such high traffic volumes I assumed the problem was caused by traffic alone and that it would rectify itself when things calmed down, I put up a temporary page and let it be. However several hours later it was still playing up, it took me a while to track down the problem but in the end deleting the cache fixed everything. It's a shame this happened because the down period of the site occurred during the period the site was on the front page of Digg. Oh well, I will know the fix for next time.
With that said, the interim period for the site, i.e. its opening month, has come to an end with quite a razzle dazzle; v0.6 of my configuration made it to the front page of Digg and fooblog consequently succumbed to the effects of lots of visitors. Fooblog uses Dreamhost as its provider which offers 2Tb of bandwidth a month; I had plenty of preparation for such an attack, or at least I thought I did. What I was not prepared for was a catastrophic failure of Wordpress 2.1.2. To save the MySQL databases from too much stress I turned on the advanced WP caching system, however when 2000 people arrived in an hour or so something went wrong and all WP pages failed to load. Due to the stresses of such high traffic volumes I assumed the problem was caused by traffic alone and that it would rectify itself when things calmed down, I put up a temporary page and let it be. However several hours later it was still playing up, it took me a while to track down the problem but in the end deleting the cache fixed everything. It's a shame this happened because the down period of the site occurred during the period the site was on the front page of Digg. Oh well, I will know the fix for next time.
Here's a fun screenshot of the traffic stats:
Posted by FofR
| Permalink
| Comments (0)
| 
