I've worked with Ruby for 12 years and I've never once had Ruby itself be the cause of poor performance. It's almost without exception the database. It might b

I've worked with Ruby for 12 years and I've never once had Ruby itself be the cause of poor performance. It's almost without exception the database. It might be fair to say a well-optimized route spends 50-70% of it's time in the interpreter, but for non-optimized routes that's far too high.