Hacker News Reader

You're talking about Ruby MRI?

Not the original MRI, but YARV. For this particular program, the performance of different language interpreters is:

MRI (Ruby 1.8) < CPython 3.5 < CPython 2.7, PUC Lua 5.1/5.3 < YARV (Ruby 1.9/2.3) < LuaJIT -joff

There is a factor of ~5x between the slowest and fastest of these interpreters. LuaJIT with the JIT enabled is ~10x faster than even its own interpreter.

View on HN

Wow, I'm not a Rubyist, so I had no idea about this. You all not only developed a faster, compliant interpreter, but Matz actually replaced MRI with an interpreter developed by a third-party as the reference Ruby interpreter? Huge props to him and the Ruby community for that.

Unfortunately, as a Pythonista (although one whose paid work is mostly in JS these days), I can't imagine that happening in the Python community (not to our credit). Too much ego wrapped up in CPython.

Doesn't that also use a JIT? Why are you comparing benchmarks versus PUC Lua instead of versus LuaJIT??

Doesn't that also use a JIT?

YARV? No.

YARV is the current official Ruby interpreter - it replaced MRI in this role from Ruby 1.9 onwards.

Weird... Sasada's presentation mentions a JIT, which is why I was confused.

(http://www.atdot.net/yarv/rc2006_sasada_yarv_on_rails.pdf page 15)

Reply on news.ycombinator.com