News for hackers. Stuff that matters.
Re:Ruby has been fast enough for 13 years by molecule on Monday May 16, 2016 @01:51PM (#11708109)
> Ruby really needs to put performance on the roadmap as a serious project.

http://engineering.appfolio.com/appfolio-engineering/2015/11...

> At RubyConf 2015 in San Antonio, Yukihiro "Matz" Matsumoto announced Ruby 3x3. The goal of Ruby 3x3 is to make Ruby 3 be 3 times faster than Ruby 2.

Re:Ruby has been fast enough for 13 years by chrisseaton on Monday May 16, 2016 @02:23PM (#11708377)
I'm not sure there are any realistic ideas to actually achieve this for MRI though (beyond the one-sentence bullet points in that article). The roadmap needs to have some roads on it rather than just wilderness!

That's speaking as someone who works full time on optimising Ruby, and wrote a PhD on it.

I think the one hope is that Evan Phoenix suggested an idea that would let an LLVM JIT optimise through the Ruby implementation, but this is a full-on research project (he said it wasn't, I'm not sure I agree), and nobody is working on it.

Re:Ruby has been fast enough for 13 years by MrBra on Thursday May 19, 2016 @02:09PM (#11732277)
You should watch the Evan Phoenix talk at RubyKaigi 2015 ("Ruby 2020") https://www.youtube.com/watch?v=QaLvtNpoc5o.

It proposes a very interesting path for Ruby to get way faster, without resorting to the JRuby implementation.

Basically what he's proposing is we could compile all the Ruby Stdlib ahead of time to a LLVM kind of bytecode. Once you do that, a JIT compiler for Ruby code could perform a way deeper optimization, because the compiler horizon-line will be stretched much further away: the compiler will be able to inspect the Stdlib bytecode and make optimizations to your Ruby code taking all that into account!

This could be a revolutionary approach for MRI, please go see the talk, it's really interesting!

Re:Ruby has been fast enough for 13 years by Freaky on Monday May 16, 2016 @03:13PM (#11708807)
Re:Ruby has been fast enough for 13 years by kristianp on Tuesday May 17, 2016 @12:07AM (#11711291)
How is GraalVM + JRubyTruffle going? It's a fast implementation of ruby.

https://github.com/graalvm/jrubytruffle

Re:Ruby has been fast enough for 13 years by astrodust on Monday May 16, 2016 @03:37PM (#11708997)
Three times faster is a good start, but honestly, if JavaScript had only come 3x faster than it was in its early days nobody would take it seriously for anything.
Re:Ruby has been fast enough for 13 years by MrBra on Thursday May 19, 2016 @02:13PM (#11732312)
Except that JS became that faster because Google invested $ millions on making it so.
Re:Ruby has been fast enough for 13 years by kristianp on Monday May 16, 2016 @11:04PM (#11711137)
Wow, I'm surprised that YARV[1] has no JIT, I thought that might have been part of the reason for the switch to it back in the day (late 2007).

[1] https://en.wikipedia.org/wiki/YARV

Re:Ruby has been fast enough for 13 years by cutler on Monday May 16, 2016 @08:54PM (#11710683)
He also said in a recent podcast that Ruby 3 will likely take 2 to 3 years to complete so don't bet the future on it.
Re:Ruby has been fast enough for 13 years by ksec on Wednesday May 18, 2016 @06:50AM (#11720991)
But they also mention it is 3x faster then Ruby 2.0! Ruby 2.1 and 2.2 actually bought in lots of performance improvement already.