It seems like you misunderstand my comment. The idea I'm getting at is that it's usually something else besides the programming that is the bottleneck, not that bottlenecks don't exist. You're going to hit architectural and database issues long before you hit Ruby's GC in most applications.