I fired up rvm and looped through my installed versions. Here are the results:
ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-linux]
real 3m11.857s
user 3m11.024s
sys 0m0.124s
real 2m54.035s
user 2m53.355s
sys 0m0.388s
real 1m59.693s
user 2m5.292s
sys 0m0.148s
real 1m50.293s
user 1m49.811s
sys 0m0.092s
Update: Evan Phoenix (@evanphx) pointed out that I was using old versions of Rubinius and JRuby. Since I'm boxed into which Ruby implementation I use (1.8.7 on our boxes at work), I wasn't thinking about keeping things up to date in my RVM installation. I've updated JRuby and Rubinius and rerun the test. The results are as follows:
jruby 1.6.0 (ruby 1.8.7 patchlevel 330) (2011-03-15 f3b6154) (Java HotSpot(TM) Server VM 1.6.0_24) [linux-i386-java]
real 1m38.390s
user 1m42.914s
sys 0m0.508s
real 1m58.138s
user 2m1.492s
sys 0m0.144s
5 comments:
Hi Pat,
If you want to use this to figure out which implementation to use, I suggest you at least try with the latest versions. Specifically, Rubinius 1.1.1 is a bit old as we're on 1.2.3 now.
- Evan
Hi Evan,
good point. I'm installing the newest rubinius with rvm now. I'll update the post shortly.
I hate to nit pick, but any chance you could wrap the whole thing in Benchmark.measure {} instead of using unix time? In the Rubinius case, you're seeing multiple threads worth of time due to the JIT (meaning time can run at 2x wall clock).
It's actually already using Benchmark.measure. I'm just timing the 10 runs of ruby-protobuf and ruby-protocol-buffer (and the accompanying analysis) so I could see the elapsed wall clock time.
I'll put together a version that uses Benchmark, but not tonight. ;)
Ah ok! Your output looks exactly like time's output, thus my confusion.
Post a Comment