Ok, my server did not stand a snowball’s chance in hell in the onslaught last night. That’s kind of sad since I had prepared for so long — but no use crying over spilled milk.
I topped Slashdot, was under “Hot News” on Digg, the top news item on TorrentFreak and was quite retweeted. The server just grinded to a halt. You might as well have unplugged it. (Which, coincidentally, I had to do to let it cool down. That took about an hour.)
Currently, the server is hanging in there — but just barely. It is working at some 95% of memory capacity, and when it hits 100, a downward spiral of death begins immediately. As it can’t service requests, the present requests take longer to process, and so capacity goes down while the flood stays constant, and so the backlog increases, et cetera.
It hits the memory ceiling a couple times a day and when that happens I need to cool it down for a while. I have ordered more memory, but until it arrives (it’s the holidays…) I need to babysit the server.
Oh, and for those who wonder what “average load 150” means: it means that the server would have needed, on average, 150 processors to handle the load over the past 15 minutes. The machine has four (!) processors. That conveys an image of just how hopelessly melted it was.