Live data from Hacker News

Ruby YJIT Ported to Rust

github.com

1–10 of 93 posts

Re: Ruby YJIT Ported to Rust

#2
"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Re: Ruby YJIT Ported to Rust

#3
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Was looking for the same thing, what does this mean for Ruby performance?

Re: Ruby YJIT Ported to Rust

#4
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

The PR itself says:

> The new Rust version of YJIT has reached parity with the C version, in that it passes all the CRuby tests, is able to run all of the YJIT benchmarks, and performs similarly to the C version (because it works the same way and largely generates the same machine code). We've even incorporated some design improvements, such as a more fine-grained constant invalidation mechanism which we expect will make a big difference in Ruby on Rails applications.

Re: Ruby YJIT Ported to Rust

#5
post #3
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Was looking for the same thing, what does this mean for Ruby performance?

[deleted]

Re: Ruby YJIT Ported to Rust

#7
post #3
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Was looking for the same thing, what does this mean for Ruby performance?

Nothing

Re: Ruby YJIT Ported to Rust

#8
post #3
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Was looking for the same thing, what does this mean for Ruby performance?

According to the post not much. The Rust version performs about the same because it generates mostly the same machine code.

Re: Ruby YJIT Ported to Rust

#9
post #3
post #2

"YJIT code ported from C99 to Rust" Beyond passing the test suite, are there more numbers to compare both versions? (e.g., compilation time, lines of code, size of binaries, performance, etc.)

Was looking for the same thing, what does this mean for Ruby performance?

YJIT benchmarks can be found at https://speed.yjit.org/

The Rust port doesn't change performance much according to the pull request description.

Re: Ruby YJIT Ported to Rust

#10
post #9
post #3

Earlier quoted context omitted.

Was looking for the same thing, what does this mean for Ruby performance?

YJIT benchmarks can be found at https://speed.yjit.org/ The Rust port doesn't change performance much according to the pull request description.

Your own link states --

Overall YJIT is 33.4% faster than interpreted CRuby! On Railsbench specifically, YJIT is 32.4% faster than CRuby!

Post reply on HN