Rails Performance and Scaling
Discussions center on the performance limitations, scaling challenges, and resource inefficiency of Ruby on Rails applications under high loads, including debates on Ruby's GC issues, comparisons to alternatives like Go or Java, and examples from large-scale deployments.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Didn't Rails have all kinds of scaling issues for non-trivial apps and loads?
Rails is slow enough to begin with.
Am I missing something? Or is rails really really expensive and inefficient?
Here's another thread talking about IO- vs CPU-Bound Rails apps from 10 months ago: https://news.ycombinator.com/item?id=42820419
Isn't the typical Rails app IO-bound?
How significant is the performance impact on a mid-large Ruby on Rails application?
If your application can’t saturate the CPU, Rails probably isn’t your bottleneck.
anyway forgive me but I was under the impression RoR had performance issues?
Rails running on vanilla Ruby does have particular scaling issues due to the limitations of the Ruby garbage collector. You hit a GC cycle after every 8MB of allocation, which typically takes around 150ms to run, so can dominate the runtime of your requests. We've had 80% of the runtime in GC, even when you include database time.This isn't necessarily a killer, but it means there's sometimes more work than you might like in scaling. There are patches to tune the garbage collector, and JRuby e
Ruby on Rails is not known for being very RAM efficient, but this is only me speculating.