Comments on: Saving Twitter in Three Easy Steps http://www.peterelst.com/blog/2008/06/30/saving-twitter-in-three-easy-steps/ Flash Platform Geek Wed, 04 Jan 2012 21:31:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Peter http://www.peterelst.com/blog/2008/06/30/saving-twitter-in-three-easy-steps/comment-page-1/#comment-18704 Peter Mon, 30 Jun 2008 21:02:41 +0000 http://www.peterelst.com/blog/?p=607#comment-18704 I see your point Phillip but lets be a bit pragmatic about this -- twitter needs to take some measures to keep the service up and running. Obviously they ultimately need to be able to handle the load and as many Scoble's as gets thrown at them but the number one goal should be to make sure they continue to have a service for them to fix. The approach right now with randomly disabling features while keeping new registrations flooding in is just pissing off users. Loved that vid by the way ;) I see your point Phillip but lets be a bit pragmatic about this — twitter needs to take some measures to keep the service up and running.

Obviously they ultimately need to be able to handle the load and as many Scoble’s as gets thrown at them but the number one goal should be to make sure they continue to have a service for them to fix.

The approach right now with randomly disabling features while keeping new registrations flooding in is just pissing off users.

Loved that vid by the way ;)

]]> By: Phillip Kerman http://www.peterelst.com/blog/2008/06/30/saving-twitter-in-three-easy-steps/comment-page-1/#comment-18703 Phillip Kerman Mon, 30 Jun 2008 20:52:02 +0000 http://www.peterelst.com/blog/?p=607#comment-18703 Sorry Peter--but that's sort of silly. I mean, sure, I suppose if everyone toned down how they use it it might help--but these are their problems to solve--and they're totally solve-able. If it was simply a problem of how we use it then it wouldn't be us.. it'd be people like scoble. Here's my vid that explains it so clearly: http://www.youtube.com/watch?v=93dGW_hDuQ0 Sorry Peter–but that’s sort of silly. I mean, sure, I suppose if everyone toned down how they use it it might help–but these are their problems to solve–and they’re totally solve-able.

If it was simply a problem of how we use it then it wouldn’t be us.. it’d be people like scoble.

Here’s my vid that explains it so clearly: http://www.youtube.com/watch?v=93dGW_hDuQ0

]]> By: Kristof http://www.peterelst.com/blog/2008/06/30/saving-twitter-in-three-easy-steps/comment-page-1/#comment-18702 Kristof Mon, 30 Jun 2008 18:48:55 +0000 http://www.peterelst.com/blog/?p=607#comment-18702 The whole thing is coded in Ruby on Rails with MySQL as the database server. The poor performance of RoR notably in database-related areas (http://www.infoq.com/articles/Rails-Performance) combined with MySQL not being a good high-performance database is killing them. MySQL only has one-way replication. This means Twitter can't build a proper round-robin system and all updates have to go through a Master database server. All reads, however, can go through any number of slaves. But it's the updates that kill Twitter, I'm sure, not the reads. Even MySQL with their poor support for indexes should be able to handle that many reads with a database farm. Twitter wrote a blog entry on their database system explaining what their problems were and how they were going to tackle those problems. The whole thing is coded in Ruby on Rails with MySQL as the database server. The poor performance of RoR notably in database-related areas (http://www.infoq.com/articles/Rails-Performance) combined with MySQL not being a good high-performance database is killing them.

MySQL only has one-way replication. This means Twitter can’t build a proper round-robin system and all updates have to go through a Master database server. All reads, however, can go through any number of slaves. But it’s the updates that kill Twitter, I’m sure, not the reads. Even MySQL with their poor support for indexes should be able to handle that many reads with a database farm.

Twitter wrote a blog entry on their database system explaining what their problems were and how they were going to tackle those problems.

]]> By: Keith Peters http://www.peterelst.com/blog/2008/06/30/saving-twitter-in-three-easy-steps/comment-page-1/#comment-18700 Keith Peters Mon, 30 Jun 2008 16:02:45 +0000 http://www.peterelst.com/blog/?p=607#comment-18700 Twitter rocks, but yeah, it's buckling under the weight of its own success. Action needs to be taken one way or another. These ideas would be a good start. Twitter rocks, but yeah, it’s buckling under the weight of its own success. Action needs to be taken one way or another. These ideas would be a good start.

]]>