artichoke VS truffleruby

The java based ruby, removes the GIL, which provides us real multithreading.

Truffleruby is "A high performance implementation of the Ruby programming language, built on GraalVM." If you prefer there is even a rust based ruby https://github.com/artichoke/artichoke

again, IMO, the microbenchmark, doesn't matter. What matters is the problem domain, whole stack and the whole "speed", including development, deployment and etc, and for some domains, ruby is the best and fast choice.

Not to be pedantic but Ruby has webassembly support, still won't work on the BEAM.

https://github.com/artichoke/artichoke

Artichoke is a Ruby interpreter written in Rust.

The owner of this reserved crate is Ryan Lopopolo who seems to indeed work on artichoke

I believe it was written mainly for/within the context of artichoke, which is an implementation of Ruby written (mostly) in Rust. It's a neat project!

I think it would be worth mentioning GraalVM and https://github.com/oracle/truffleruby in competitors section.

GitHub page has some info: https://github.com/oracle/truffleruby#current-status

My question is, how viable is TruffleRuby vs JRuby?

I wonder why GraalVM is not more often used for these speed critical cases: https://www.graalvm.org/python/

Is the problem the Oracle involvement? (Same for ruby https://www.graalvm.org/ruby/)

Looks like it’s still a WIP

https://github.com/oracle/truffleruby/commits?author=eregon

this comes at the cost of boxing ints inside Integer, though.

So, if you ignore for a moment primitives types, whenever you have generics, everything boils down to a single method accepting Objects and returning Objects. What the JVM does is to do runtime profiling of what actually you are passing to the generic method, and generate optimized routines for the "best case". In theory this is the best of the two worlds, because like in general you will have a single implementation of the method (avoiding duplication of the code), but if you use it in an hot spot you get the optimized code.

In a way, it is quite wasteful, because you throw away a lot of information at compile time, just to get it back (and maybe not all of it) at runtime through profiling, but in practice it works quite well.

A side effect of this is this makes the JVM a wonderful VM for running dynamic languages like Ruby and Python, because that information is _not_ there at compile time. In particular GraalVM/TruffleVM and exposes this functionality to dynamic language implementations, allowing very good performance (according to they website [1][2], Ruby and Python on TruffleVM are about 8x faster than the official implementation, and JS in line with V8)

[1] https://www.graalvm.org/ruby/

I opened a ticket some time ago about performance with Jekyll and liquid templates. At least in that case, yjit was way faster. I'm happy to retest though. Anything that would make my jekyll builds faster would help.

https://github.com/oracle/truffleruby/issues/2363

Here's a benchmark [1] done in Jan'22 against many ruby implementations, truffleRuby [2] seems to be way ahead in most, and at least ahead in all. Why truffleRuby isn't talk about much here?

[1] https://eregon.me/blog/2022/01/06/benchmarking-cruby-mjit-yj...

[2] https://github.com/oracle/truffleruby