I was looking over Antonio's new shootout results and I'd like to ask that we remove bm_prime entirely. It's a red herring benchmark entirely now, because nearly all implementations timeout on it, except for 1.9.2 because in 1.9.2, Prime is entirely in C.
So all it proves is that 1.9.2's Prime C code is faster than ruby code. It doesn't serve as a anything close to a reflection of overall implementation performance.
Even the benchmark itself has comments saying that it's now tuned to show great performance on 1.9.2, but timeout everywhere else.
For these reasons it's especially misleading and should be removed. If it's not removed, then 1.9.2 should use the Prime ruby code all other implementations use, NOT it's C code.
- Evan Phoenix
A quick comparison on primes 3000 shows 1.9.1 & 1.9.2 are ~ 400x faster than 1.8.7. Not useful for the casual observer. I agree with Evan that we should deprecate this benchmark.
A quick comparison on primes 3000 shows 1.9.1 & 1.9.2 are ~ 400x faster than 1.8.7.
On Tue, Jul 20, 2010 at 12:17 PM, Monty Williams <monty.w...@gemstone.com> wrote:A quick comparison on primes 3000 shows 1.9.1 & 1.9.2 are ~ 400x faster than 1.8.7.For some reason I don't think I received Evan's email. I agree that we can exclude/remove the benchmark.
The GitHub project is located at http://github.com/acangiano/ruby-benchmark-suite
You received this message because you are subscribed to the Google
Groups "Ruby Benchmark Suite" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at
Would you consider removing the results from the current shootout?
On Tue, Jul 20, 2010 at 12:33 PM, Evan Phoenix <ev...@fallingsnow.net> wrote:Would you consider removing the results from the current shootout?I would consider adding a warning note to the time result section.
I'd like if you would, so that people know how to interpret the data better.