This gets said here a lot. What about GitHub and Shopify, and ...? Are those toy apps?
[1] http://www.slideshare.net/jduff/how-shopify-scales-rails-204...
*From an episode of Ruby Rogues with Zach Holman
You seem to imply Ruby's/Rails' speed matter?
Usually, the DB is the limiting factor in most web applications, few should need to execute more than a few milliseconds of (even) Ruby per page load. That is why people use scripting languages, after all.
Shouldn't this slowdown be a problem in the ORM for this version? I'd look at access patterns for normal requests for the new Rails version and the old. How has the SQL changed?
Sure, Twitter is different since that probably is processor bound.
(Since RoR is a popular framework with lots of eyes, there shouldn't be something simple with e.g. configuring the web server, locking etc.)
Actually, they escaped to the JVM, and if their job reqs are any indication, they hire massively for Java engineer positions and hardly at all for Scala ones.
I wouldn't call that chickening out, more common sense.
Rails is great for prototypes and toy apps, but once you start needing scale, it's simply not up to the task.