The cardinal numbers are most likely all bogus.
I'm surprised that any benchmarks ran at all.
The current cardinal implementation is extremely minimal. Basically simple arithmetic.

Kevin

Nicholas Clark wrote:
There's a benchmark of Ruby implementations at

http://www.antoniocangiano.com/articles/2007/02/19/ruby-implementations-shootout-ruby-vs-yarv-vs-jruby-vs-gardens-point-ruby-net-vs-rubinius-vs-cardinal

(or http://xrl.us/uy5m )

There's a comment from Matt Diephouse

  Did you build an optimized version of Parrot to use with Cardinal?
  By default, Parrot builds with all optimizations off and with all
  debug flags on. This makes it slower but makes development a lot
  easier.


The answer was "no"

I was wondering - are people doing benchmarks more likely to be using
release versions of parrot rather than svn head? If so, would it be a
good idea for positive publicity's sake to have the release versions
default to optimise?

Alternatively, given that gcc is capable of building with both debugging
and optimising, and a good number of people benchmarking will be on Linux,
would it be viable to make the default with gcc to be "-g -O2"?

Either way could try to skew third party benchmarks (and the unpublished
private benchmarks we don't even know about) in Parrot's favour.

Nicholas Clark

Reply via email to