Of course; this:
Use Something Else.
I worry that if they went hand-rolled assembly, everyone would be jumping in that bandwagon.
The poster asked for similar resources on scaling Rails up; maybe something like https://github.com/blog/117-scaling-lesson-23742 or http://axonflux.com/building-and-scaling-a-startup would have been useful.
I sincerely doubt that the top-poster has Twitter-level problems or resources. He may have a Rails site that's crapping out under load, and needs resources for optimizing both application performance and database access.
"Just move everything to Java" is a meaningless answer. It doesn't help him at all, not unless he's got a year and change to retrain/rehire his engineers and completely rebuild his application.