3 ms·
Was looking for the same thing, what does this mean for Ruby performance?
by tmikaeld 5y ago
Was looking for the same thing, what does this mean for Ruby performance?
- deleted 5y ago[deleted]
- block_dagger 5y agoNothing
- ModernMech 5y agoAccording to the post not much. The Rust version performs about the same because it generates mostly the same machine code.
- Rafert 5y agoYJIT benchmarks can be found at https://speed.yjit.org/ https://speed.yjit.org/ The Rust port doesn't change performance much according to the pull request description.
- npalli 5y agoYour own link states -- Overall YJIT is 33.4% faster than interpreted CRuby! On Railsbench specifically, YJIT is 32.4% faster than CRuby!
- WJW 5y agoYes, but YJIT in rust is the same ~33.4% faster than vanilla CRuby than YJIT in C. The rewrite into Rust is expected to make YJIT easier to maintain and that may in turn make possible further improvements to code generation, but the rewrite generates the same machine code (and therefore the same speedup) as before.
- ewalk153 5y agoI didn't know this was public, sweet! Nice that the tooling that generates this report is also published: https://github.com/Shopify/yjit-metrics https://github.com/Shopify/yjit-metrics
- rvz 5y agoIt means completely nothing for performance.
- pizza234 5y agoVery likely, the performance of a JIT comes from: - the architecture of the JIT itself - the generated code AFAIK, the Rust YJIT doesn't change any (they explicitly say that the generated code is approximately the same), so there no significant difference in performance should be expected.