5 ms·
Oh, that meme is old, sorry to say. Here's a nice blog post about ruby outperforming C with the new JIT compiler. Fun times :) https://railsatscale.com/2023-08
by ckolkey 2y ago
Oh, that meme is old, sorry to say. Here's a nice blog post about ruby outperforming C with the new JIT compiler. Fun times :)
https://railsatscale.com/2023-08-29-ruby-outperforms-c/ https://railsatscale.com/2023-08-29-ruby-outperforms-c/
- slashdev 2y agoIn very specific, very limited cases. I remember when these claims were made for Java twenty years ago. It’s still slower than C, most of the time. Some things don’t change.
- neonsunset 2y agoRuby YJIT is slower by multiple orders of magnitude if we look at more than a single constructed example. In addition, the blog post measures the cost of avoiding doing the interop, which allows wins as the compiler improves in the case of short-lived calls implemented in a native component. This, however, is not exclusive to Ruby and statically typed JIT or AOT compiled languages benefit from this to a much higher extent. https://benchmarksgame-team.pages.debian.net/benchmarksgame/box-plot-summary-charts.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...