Home > Ruby on Rails, Social Networks > Twitter is giving Rails a bad name

Twitter is giving Rails a bad name

twitterificUggh. Rebuild it already. Its only a few actions. It wasn’t built for this kind of app.

Python, C, Perl, whatever.

Categories: Ruby on Rails, Social Networks Tags:
  1. July 2nd, 2008 at 13:56 | #1

    You sure it’s not the other way around? Did you see this? http://www.avnetlabs.com/php/php-framework-comparison-benchmarks

    Check out CodeIgniter’s benchmarks at the very bottom when using various ORM / code cache.

  2. tony
    July 3rd, 2008 at 11:30 | #2

    Rails is very fast by default in my experience even under moderate high load but if you need to get killer performance you simply break out of ActiveRecord and use plain SQL and turn on caching.

    In Twitter’s case they have extreme activity on a simple app. I’d load balance, memcached, and if that didn’t work slap C in front of it.