jruby woe

JRuby limited openssl loaded. http://jruby.org/openssl
gem install jruby-openssl for full support.
# A fatal error has been detected by the Java Runtime Environment:
# SIGBUS (0x7) at pc=0xf6b70c53, pid=11129, tid=4140485488
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode linux-x86 )
# Problematic frame:
# C [libzip.so+0xbc53]

meant “you can’t update your jruby distro while also using it”

rubygems woe

WARNING: RubyGems 1.2+ index not found for:

RubyGems will revert to legacy indexes degrading performance.
Bulk updating Gem source index for: http://gems.rubyforge.org/
ERROR: While executing gem … (Gem::RemoteSourceException)
Error fetching remote gem cache: bad response Gateway Time-out 504 (http://production.s3.rubygems.org/yaml)

meant “rubygems.org is temporarily down right now” (I think, since it was reproducible from several locations, then went away).

gcc woe

Error: suffix or operands invalid for `push’
meant “you are using an “old” locally installed version of gcc, which doesn’t work with your new version of the operating system somehow”

Linux rails benchmarks using various VM’s

I took the various VM’s for a test drive the other day, running some rails benchmarks.

Tested were rubinius 1.0.1 (with JIT),
jruby 1.6.0.dev (ruby 1.8.7 patchlevel 249) (2010-06-03 2b166c9) (Java HotSpot(TM) Server VM 1.6.0_18) [i386-java], ruby 1.8.7p249 (linux, 32-bit), and ruby 1.9.1p376 (linux, 32-bit).

All were tested in a Virtualbox 3.2.2 with 2 cpu cores assigned to it, using the rails benchmarks from the ruby benchmark suite (rails 2.3.8, single threaded).
Linux version 2.6.32-22-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010
Here’s how they fared:

Interesting to note is that 1.9.1p376 is a bit faster for most things, 1.8.7 isn’t far behind, and is fastest for running the unit tests.

Jruby and rubinius, despite making great strides in execution time, are still a bit slower.

I had expected jruby to do better based on http://blog.pluron.com/2009/05/ruby-19-performance.html but it seems that, for me at least, it still falls behind (I’ve heard a few other people with similar results).

Also note a windows benchmark of the same.

Any thoughts?

Any other rails benchmarks you think should have been included?