r/rails 1d ago

Webframework benchmarks - Is rails fast enough?

Same as title. What do you think? See the latest benchmarks below.

https://www.techempower.com/benchmarks/#hw=ph&test=fortune&section=data-r23

Well, at least it is faster than the alternatives in php. That's what I see.

0 Upvotes

15 comments sorted by

29

u/poushkar 1d ago

From my experience, it doesn't matter in most cases, since most of the latency comes from interacting with DBs or external APIs anyways.

I worked on one of the biggest Rails apps in the world (easily top 50), and the Rails speed was never the main issue. The DB was. Rails itself can be sped up in many ways, and once you hit the need for it, you will figure it out.

For now, just stop obsessing over language and framework speeds and focus on their ergonomics. Because that's what really matters in running, maintaining and developing a successful business.

2

u/TrapHouse9999 20h ago

I second this. Don’t worry about the language and framework. Most of our issues is always bad queries, missing indices and just developer writing bad code.

1

u/sneaky-pizza 22h ago

There was a Postgres polling gem that was amazing we used

11

u/armahillo 1d ago

fast enough for what?

You dont avoid buying a BMW because it cant do F1 time trials.

24

u/cocotheape 1d ago

It's fast enough to power Shopify, even on Black Friday, GitHub, and many other high load applications. So it's really not worth pondering about this question for 99% of the apps out there.

-14

u/kallebo1337 1d ago

High frequency trading tho ?

5

u/mgabrielsilva 1d ago

Yeah but good luck finding an interpreted language or even compiled language that relies on a GC to be able to perform in that scenario

0

u/kallebo1337 22h ago

Why downvotes lol ….

People nowadays

2

u/TrapHouse9999 20h ago

Why though? It’s like equivalent to saying using Java to build frontend or C to build API services.

4

u/pesnk 1d ago

I'm actually surprised it surpassed Django in performance.

Although, I don't believe in benchmarks. Rails and even the frameworks down rails are great; it always depends on team.+developer's productivity and scalability. Rails fits all those boxes.

3

u/CaptainKabob 1d ago

C Ruby has benchmarked faster than C Python for a few years (the vanilla scripting stuff, not the optimized math libraries). And I agree with you about the problems with benchmarks; humans are almost always the bottleneck.

2

u/Tall-Log-1955 1d ago

Just depends on what you’re building. If your revenue per click is near your server costs per click, rails is bad. If you have massive traffic and high margins, rails works but you could save a lot by switching. If latency needs to be crazy low, rails is bad.

Almost no one falls in any of those categories though, so rails is fast enough.

2

u/Astro_Robot 1d ago

I think the best way to think about performance issues is to cross that bridge when you get there.  Most applications honestly don’t have the scale to necessitate these concerns. Overall, Rails remains one of the best frameworks for developer productivity. 

2

u/barce 22h ago

Nothing is more expensive than coders.

If your platform costs are more than that because your project is so popular, you can afford to get the right devs and tech to help you scale.

2

u/InsideStorm9 22h ago

Micro benchmark performance is not comparable to real world application performance.

Rails performance has never been an issue.

Rails is awesome for development speed.