Comments on: Ruby Implementations Shootout: Ruby vs Yarv vs JRuby vs Gardens Point Ruby .NET vs Rubinius vs Cardinal

By: Lorenzo

Lorenzo — Tue, 30 Nov 1999 00:00:00 +0000

Very intresting, thanks for doing this Antonio

By: Michael Silver

Michael Silver — Tue, 30 Nov 1999 00:00:00 +0000

Great to see how the different implementations compare. It is also another example of the speed boost Yarv will provide.

In another comparisons I saw, Ruby was actually the fastest scripting language, between PHP and Python, when used with YARV.

By: Asd

Asd — Tue, 30 Nov 1999 00:00:00 +0000

The new JRuby compiler stuff should make it a lot faster.

By: Tom

Tom — Tue, 30 Nov 1999 00:00:00 +0000

Awesome benchmarks. Ruby 2.0 is going to be fantastic then! Thanks so much for doing this.

By: Giovanni Intini

Giovanni Intini — Tue, 30 Nov 1999 00:00:00 +0000

I was worried Yarv was not going to be fast enough, your tests show otherwise, I will sleep better

By: nobody

nobody — Tue, 30 Nov 1999 00:00:00 +0000

Michael Silver:
Would you care to publish the url? Seems interesting.

By: Charles Oliver Nutter

Charles Oliver Nutter — Tue, 30 Nov 1999 00:00:00 +0000

Very interesting results, and very promising for JRuby. I’d like to point out the following details about the JRuby results:

- We’ve only recently started to work on performance; so these numbers actually look pretty good to me.

- This is JRuby in interpreted mode, compared to YARV, Ruby.NET, and Rubinius running with compiled code. Our prototype compiler has shown we can improve speed many times.

- Some of these are IO bound, and our IO subsystem is in bad need of improvement. But we know what’s wrong, and we know we can fix it.

- We’ve focused on correctness, which counts for a lot. We’re the only alternative implementation that can run Rails out of the box. Now for the next
step

But it’s great to see these numbers and see how we compare. It will motivate us to continue working (and I see from the mailing lists and IRC channel that’s already happening

By: Evan Phoenix

Evan Phoenix — Tue, 30 Nov 1999 00:00:00 +0000

Just wanted to drop a note to let people know they shouldn’t worry about rubinius. The project is so young that we’ve not yet begun to perform any of the normal speed optimizations such as selector caching. These optimizations are now being added, and I’ll ask that hopefully the tests be rerun against rubinius soon with these in place.

By: Antonio Cangiano

Antonio Cangiano — Tue, 30 Nov 1999 00:00:00 +0000

Hi Charles,

thank you so much for stopping by and adding details and a good contribution to the discussion. I’m glad that you found this post somewhat useful. I believe JRuby is very promising, in fact it’s always a part of my slides whenever I present Ruby and Ruby on Rails to meetings and conferences.

By: Antonio Cangiano

Antonio Cangiano — Tue, 30 Nov 1999 00:00:00 +0000

Hi Evan,

thanks for commenting. As I wrote in the disclaimer “… some of them haven’t been optimized for speed yet”, and Rubinius, being a fairly young project, is one of them. I plan to re-run these tests periodically so there will be plenty of space for testing improvements.

Also, feel free to drop me a line by email whenever you feel like Rubinius is ready for another test.

Thanks,
Antonio

PS: we’re being slashdotted, so hopefully this will give more exposure to each single project as well.