Feed

Oh Noz! Mah Twittah Iz Daon

Posted on May 26th, 2008 in Coffee_Powered_Musings by megalar

From is twitter dying?:

It seems that everyday now there is a problem with . Not too long ago I heard say that if the public jumps on it will go down. Is that what is happening? Today their main database, db006, went down. I always know something is wrong when Twhirl wont let me get tweets even if I haven’t gone over the limit.

It seems from the that people are pretty understanding when it comes to . I tend to agree with them, to a certain point. Free services such as Wordpress.com have brought expectations up on free services. Although, the can be quite frustrating.

Why can’t they just get some decent hardware and produce some better uptime? I’m sure it wouldn’t be hard to raise some money.

Lets take a closer look at this:
“Not too long ago I heard say that if the public jumps on it will go down. Is that what is happening?”
Fearmonger.
“It seems from the that people are pretty understanding when it comes to .”
Look again, people are acting like children. Everything is normal.
“Free services such as Wordpress.com have brought expectations up on free services.”
11,000 nails per hour. That’s an old article. How many hits per hour you think it gets now? My money is on more. You think wordpress gets that kinda traffic? Doubtful. If for no other reason than the posts are usually longer than a tweet so people take longer to read them.
“Why can’t they just get some decent hardware and produce some better uptime?”
You are confusing the issue. They are in the middle of an almost complete architectural redesign. Also, can you imagine the size of the db? I can’t. You ever do a backup restore of a db larger than ~100mb? It takes a while.

I don’t mean to pick on you dude. Truth is, I picked your post because it was the first in the link list on man down. Please don’t take all this the wrong way. I think most of the we see about this outage is due to ’s new policy of trying to be more transparent about service problems. And for the record, I doubt is dying. But what do I know.

Tags: , , , , , , ,

Add a comment on FriendFeed




7 Responses to 'Oh Noz! Mah Twittah Iz Daon'

Subscribe to comments with RSS or TrackBack to 'Oh Noz! Mah Twittah Iz Daon'.

  1. Josh said,

    on May 27th, 2008 at 8:35 am

    I know twitter isn’t dying. I was bringing it up because they had to do unscheduled maintenance on their main database yesterday due to overuse. This reminded me of when I heard John Dvorak make that comment about the general public. And as for Wordpress, I’m sure if they got that kind of traffic Matt would jump on it pretty quick.

  2. Josh said,

    on May 28th, 2008 at 3:19 am

    Thanks for the critique though

  3. megalar said,

    on May 29th, 2008 at 10:56 pm

    I’m sorry if it seemed like I was jumping on you dude. Truth is, I thought your article was well written and because of that it would allow me to address the issue. Your post outlined very nicely the general “Twitter is Dead!!!!” paranoia that was running wild through the blogosphere. So thanks for allowing me a great place to jump into the conversation.
    On a side note, I like your blog so I’ll be adding it to my blogroll and I’d like to encourage anyone reading this to check it out.

  4. Josh said,

    on May 30th, 2008 at 7:30 am

    It’s cool and no problem, I’m glad you contributed to it like you did. I was surprised to see all the traffic that I got on that post. I guess the link from ‘man down’ helped a lot.

    Thanks for the link. I just redesigned the blog not too long ago and had originally intended to hold off on the new look until i go with a new domain in about a month. When I do finally everything squared away with that I’ll be sure to send you the new link.

  5. Josh said,

    on May 30th, 2008 at 9:02 am

    Just an update on the actual argument here — Matt was on the Wordpress Weekly podcast this week and he said they serve more than half-a-billion requests per day. That is over 20 million requests per hour.

  6. megalar said,

    on May 30th, 2008 at 3:53 pm

    Thanks for the update Josh. From my original post “11,000 nails per hour. That’s an old article. How many hits per hour you think it gets now? My money is on more. You think wordpress gets that kinda traffic? Doubtful.” Looks like I guessed wrong. :D As I said though, that was an old article and I honestly don’t know how many db hits an hour twitter is taking now.
    If its a comparable number to wordpress then we have to ask the question “how is it different?”. Possible answers: hosting, number of employs (I know twitter has 16 but I’m unsure about Automattic), architecture and backend (ruby on rails vs. php). We know for certain that the dev community behind wordpress is larger and that certainly makes a difference. Perhaps it is the key difference.
    Wordpress is open source and like any open source project with a large following they reap the benefits, you basically have a whole army of geeks testing, tweaking, and modding your code for free. This makes me look at gillmor-gang-050808 a bit differently. They were discussing nationalizing twitter and while that idea is silly, a distributed open source model is not. If twitter had the power of the OSS movement behind it, combined with its huge following (which would grow exponentially once JohnQ could run his own twitter install that had two way aggregation with 1) the central twitter server and 2) customizable networks of twitter servers) there would be no stopping it. The users would be much happier because their networks could ping each other even if twitter central was down.
    I know some people will say I’ve gone way out there now and gotten too far away from what twitter actually is. But have I? Perhaps I have, it is almost 4am afterall.
    Thoughts anyone?

  7. megalar said,

    on May 30th, 2008 at 9:35 pm

    I had forgotten that twitter opensourced their messaging queue Starling.
    I did a little googling for decentralized twitter and the very first result was very interesting, particularly the comment from jstanforth:

    Thought about this a bit this afternoon (Norton apparently takes HOURS to virus-scan 1.7m files… argh), and my ideas are similar but still not completely decentralized. Seems like a system of root-servers (a la DNS) could manage the @username repository and auth mechanisms (to avoid users impersonating other @usernames on the distributed servers), and then a series of widely-distributed servers could mesh via XMPP using the root-server auth to get subscriber lists, etc. The benefit here is that those with thousands of followers would be the ones upgrading their own servers, and others who either don’t post frequently or don’t care about the lag can just remain on the main (current) Twitter site. So, Engadget sets up their own server, and during MacWorld, all their followers get tweets best-effort pushed directly from their distributed server to all their followers. If they want to support more followers without lag, they can upgrade their own systems— the followers don’t need to upgrade anything at that point, which keeps the upgrade burden on the right side of that equation (i.e., if it’s slow, complain to Engadget, not to Twitter or whomever is running the top-level root servers). It also means that Engadget followers don’t overwhelm the overall system during high-volume conference weeks, because their added traffic is mostly segregated to their own sub-networks.

    This approach essentially builds a caching layer for the current Twitter architecture, so while the many distributed servers use a best-effort push directly to the other specified followers, every tweet would ALSO be pushed up to the root servers for general users, long-term archive, etc., the way that Twitter currently works. If this were built outside of Twitter, presumably the Twitter API would enable pushes directly to Twitter when the system is working normally, and allow tweets to be queued and re-delivered asap if Twitter is unstable/unavailable at that moment. So, yes, there’s a lag in this latter case, but in the current system, there’s no posting at all in that case.

    Then build the root-server level with S3, EC2, SimpleDB, etc, and store the tweet archives as RSS and the follower lists as OPML, and you can then serve them directly from S3 and — I think? — support almost every idea I’ve heard from Dave so far, including enclosures, etc.

    Can you think of reasons this wouldn’t work? Or even better, better ideas to improve upon this?

    Jabber. Groovy.
    And even better Blaine Cook has long endorsed the idea:

    Blaine from Twitter here. FWIW, we have an XMPP PubSub service that allows you to subscribe to public timeline updates. It’s currently in “beta”, and we’re rolling it out as people request it. As far as social network federation goes, it’s something that I’ve talked publicly about since early last year; see my talk from XTech ‘07 for a general direction, and some of the discussions that came out of the Mediamatic gathering in December for more details. Ralph Meijer (formerly with Jaiku) and I have been discussing the possibility of federating micro-blogging networks since before we met at XTech last year, and really the barrier to doing it is partially a business discussion, and partially a lack of implementors.

    And that’s just from the first result in Google. 94,200 to go. :D
    So… I’ll add some quotes and narrow it down to 5,850 I’ll do some more looking, but it seems to me that with this much out there we aren’t far away from seeing this implemented. I hope so anyway.

Post a comment