About the downtime

Well there has been an ongoing bug with the way the site works for a while and recently it decided to rear its ugly head while Digg was having their second glance at "What slows windows down". I take pride in my programming

Well there has been an ongoing bug with the way the site works for a while and recently it decided to rear its ugly head while Digg was having their second glance at "What slows windows down".

I take pride in my programming of the site because it does work well for 95% of the time. Occasionally though, when ASPNET purges it from memory (for freshness), it ends up in a crazy infinite loop of loading up, destroying all CPU cycles in its path. When thousands of people are requesting the site at the same time, this effect is magnified.

This wouldn't be so bad if I wasn't running this off a shared hosting platform...

The guys at Hostek had no choice when the application went wild to shut it down because I was affecting other people on the server as me. I cannot blame them at all for this and I hope you don't either.

My programming == my fault.

Speaking of my programming, I'm going to be spending the next couple of days chasing the bug out so this never happens again. If anybody out there knows a lot about the ASPNET Cache (especially involving concurrency and IIS-started clean-ups), please leave me a comment. ThePCSpy.com needs you!

Normal service shall commence when I've got the issues out the way.

Post apocalyptic update

Well it has been a few days since the troubles and I've reprogrammed a lot of the concurrency-important sections of the site and (barring a few hiccups along the way) the site seems to be the healthiest it has ever been.

I'm still working out a few really random exceptions but everything should be cool now.