When I posted on Digg asking Diggers to help crash my site, and to see how much my little server can take, I wasn’t expecting almost 2200 Digg’s and 254,000 hits and 29,000 visits (awstats). I wrote a little script to flash my server everytime it got overloaded, which was approximately every 5 minutes. By six hours after my post got on the frontpage of Digg, My server operation went back to normal, still getting 50 hits per minute.

So I think it’s safe to assume that my server is yet not ready for Digg and it’s wrath ;). Yes I ordered my Quad core system and yes I will take a note to increase my bandwidth. Till then you will have access to never before scene of my site dying slowly…

First start with awstats picture:

Digg FrontPage:

And Finally Sitemeter Stats, Where there is a huge discrepancy because Sitemeter counts each visit in terms of fully loaded website, whereas Awstats counts in terms of server hits; this is my understanding.

You see that little slope from 9 to 2. That’s when I fell a sleep and my server was overloaded like crazy. Than I woke and started the script and things got a little bit better, and than I went back to sleep.

So before I do my next digg-effect experiment, I am slowly prepering myself with all kinds of tools and books and hardware. I will still follow the three rules 1) I won’t use anything other than Apache 2) I will run it from home 3) It will still run on a windows box load balancing with several linux machines.

To the naysayers, I made exactly 15 bucks from ads during the digg effect. I make more money per minute in my real job. So if you have a problem with my site having adds (which I won’t remove), either use greasemonkey or don’t go to Digg.com. Digg.com has more ads in a more obstructing manner than mine does. Boohoo!

cheers,

pavsHacking Hacking Linux News News Software Review Hacking Tools Linux News News Software Review