DEV Community

loading...

Discussion on: On Death and Dying: Ruby on Rails

Collapse
nbageek profile image
Patrick Minton

This is almost never a relevant benchmark when choosing a framework for building an internet site. And if this kind of performance is crucial to your application, then you shouldn't be choosing Python, PHP, or JS either. If how fast your code crunches numbers or iterates through loops is important, then you are doing something very niche and you should be using a compiled language anyway.

There are just soooooo many bottlenecks on website performance that come before the language's server-side runtime performance that optimizing for that particular aspect is a waste of time.

Collapse
elmuerte profile image
Michiel Hendriks

Who's picking frameworks here? We have an application, and different ways to run them. I'm just wondering what options are being used in the wild.

Have you tried running your long running internet site application on JRuby, or CRuby with/without JIT?

FYI, modern JIT compilers can produce better performing machine code than a AOT compiler. This is due to the fact than a JIT compiler can continuously create tracing profiles and re-compile the code. So there is definitely a benefit of not using a "compiled language". (I assume you mean a language which compiles to machine code rather than an intermediate byte code.)

There is also more to a runtime than just computation. There is also memory management and garbage collection, or creating more CPU cache/memory localized code. This leads to less system resource pressure. Sure, your IO will always be a bigger performance issue. But being able to resort to smaller and less loaded VMs has a significant benefit in your wallet and scalability.