Skribit Blog

Some of you might have noticed that we had some uptime problem today.  The cause of the interruption was that one of our Skribit bloggers had a post that got dugg heavily today:

Here’s where we are at the end of the day:

• First, congrats to Jobmob on getting their post dugg.  Great post.
• Despite the downtime on our site and our widget, this did not affect the page load times of any of our user’s blogs.  We consider that a very (very) minor victory.  I wish I can promise you that we’ll never suffer from downtime again, but that is unrealistic.   What is realistic is to expect that your site will not be negatively affected when we have problems on ours, and that we’ll fail as gracefully as possible when something on our side does go wrong.
• About an hour ago, we made a patch to Skribit which should withstand the level of activity we saw today, and we’re continuing to explore other ways of squeezing more performance out of the system.

Lastly, I want to express that we don’t consider any downtime from a blog being dugg as being acceptable level of service.  We should be able to withstand many diggs without any noticeable affect on site performance, and are taking whatever action necessary to make that happen.