Comments on: Ruby on Rails Hits a Wall; Twitter Stutters http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/ Musings on the craft and business of software development Wed, 20 Aug 2008 14:07:20 +0000 http://wordpress.org/?v=2.5.1 By: Jeff McNeill » Blog Archive » links for 2007-06-04 http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1913 Jeff McNeill » Blog Archive » links for 2007-06-04 Mon, 04 Jun 2007 13:19:13 +0000 http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1913 [...] Bob On Development » Ruby on Rails Hits a Wall; Twitter Stutters Apr 2007 (tags: rails) [...] [...] Bob On Development » Ruby on Rails Hits a Wall; Twitter Stutters Apr 2007 (tags: rails) [...]

]]> By: random8r http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1049 random8r Mon, 16 Apr 2007 13:12:11 +0000 http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1049 Um actually you've always been able to sustain multiple connections simultaneously. This is part of Ruby. It just wasn't as "wonderfully easy" as the rest of Rails is, because it's rarely been a common problem. Um actually you’ve always been able to sustain multiple connections simultaneously. This is part of Ruby. It just wasn’t as “wonderfully easy” as the rest of Rails is, because it’s rarely been a common problem.

]]> By: Warren Seen » Blog Archive » Rails, Twitter and the 800lb Gorilla in the Room… http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1036 Warren Seen » Blog Archive » Rails, Twitter and the 800lb Gorilla in the Room… Mon, 16 Apr 2007 01:25:19 +0000 http://bobondevelopment.com/2007/04/13/ruby-on-rails-hits-a-wall-twitter-stutters/#comment-1036 [...] of “no premature optimisation” to language and platform selection? If Twitter had chosen an “enterprise” class platform and tried to architect for 11k reqs/sec, chances are they would still be [...] [...] of “no premature optimisation” to language and platform selection? If Twitter had chosen an “enterprise” class platform and tried to architect for 11k reqs/sec, chances are they would still be [...]

]]>