Lakers victory defeats World Cup Twitter records

"Sports fans are raising Twitter's usage to a new level: A goal by Japan's World Cup soccer team against Cameroon on June 14 led to a record number of "tweets per second" for Twitter, only to see the record beaten again a few days later when the Los Angeles Lakers defeated the Boston Celtics in the deciding game of the NBA championships.

The Japanese goal, which led to a 1-0 victory for the team, resulted in a peak of 2,940 tweets per second in the 30 seconds following the game according to a post on the Twitter blog."

Source - Cnet

Ah, I see. The Twitter Fail Whale appeared recently again after a very long time, this explains it.

So the world cup is going on... and Twitter is once again unprepared.

Ah, I see. The Twitter Fail Whale appeared recently again after a very long time, this explains it.

So the world cup is going on... and Twitter is once again unprepared.

As far as I know, Twitter was/is a Rails application and some parts of it has been rewritten to increase performance.

I think the problems still is that it was not written with this kind of ridiculously high expansion in mind.

Rail is a great environment to quickly do things that would take ages to do without Rails. But you pay in reduced performance. It can anyway be a good idea to start a web application using Rails because of the reduced development time and shorter time to market.

Scaling problems can be dealt with once the money is ticking in. Scaling problems are also, to some extent, solved by the development of more powerful hardware that typically double performance every 18 months so if your amount of traffic are increasing less, no problems,

But the twitter traffic is increasing much faster than that...

Martin