Performance Update
Over the weekend we made a bunch of bug fixes and improvements to Twitter which resulted in more reliability in message delivery―this increased overall traffic.
Ordinarily, increased reliability and traffic is a good thing. However, this comprehensive delivery of messages together with two severe cases of abuse strained Twitter's primary database enough to degrade performance.
Today we worked to address these performance and reliability issues. We also took notes and preventative measures so Twitter will be smarter about this stuff next time.
The web site is feeling snappy and back to normal which means we will now be investigating and finding a fix for the SMS issues which some folks have been reporting.
It doesn't always feel like it while we're digging in and making small improvements but we are building a better, more reliable service every time we fix a bug.
Ordinarily, increased reliability and traffic is a good thing. However, this comprehensive delivery of messages together with two severe cases of abuse strained Twitter's primary database enough to degrade performance.
Today we worked to address these performance and reliability issues. We also took notes and preventative measures so Twitter will be smarter about this stuff next time.
The web site is feeling snappy and back to normal which means we will now be investigating and finding a fix for the SMS issues which some folks have been reporting.
It doesn't always feel like it while we're digging in and making small improvements but we are building a better, more reliable service every time we fix a bug.
16 Comments:
any details on the abuse? what happened? Is this what is being ref'ed in the error message for the disabled search?
John Minnihan
Yes, one of the cases of abuse had to do with our publicly available search feature. Essentially, someone had a wrong-headed way of going about trying to find a whole bunch of people at once on Twitter. The other case was a simple request automated to be performed a zillion times.
The key issue for us in both cases is to make sure performance doesn't slow down for people when events like this take place.
So... why hasn't the issue with dropped tweets in the timeline been fixed? Some tweets are still not appearing in my timeline, even though the tweets appear in the timeline of the friend. What's the deal?
So Biz, will you be posting those numbers you mentioned any time soon?
Shel, we posted a graph illustrating relationship distribution among Twitter users along with a few others. We've dug up the data on updates per day and geographic distribution as well and we'll be posting them too.
Hi simx, the issue regarding missing updates has been fixed. However, for some folks we'll need to clear the cache--which we're doing.
@biz: That doesn't seem to explain why tweets are *still* getting lost, though, does it? I'm talking about new tweets, one which was made just a few minutes ago, are still not showing up in the timeline.
Wouldn't the cache only affect older tweets?
i'm still missing tons of tweets...clear my cache, please and thank you!
how long until twitterim gets fixed?
Missing @'s have not been fixed. I have not seen 1 @ for a couple days.
It would be nice if they were fixed.
How is the reliability since Twitter left Joyent hosting?
Where are you twitterIM? I miss you!
Performance seems to have tanked today valentines day in Australia...
Guys performance has been crap today in Australia & since the feature upgrade, which we love, stability very bad.
But we still <3 you
Where are you twitterIM?
Your reliability is suffering. That's a major cornerstone for any business.
Post a Comment
Links to this post:
Create a Link
<< Home