Skip to content
September 21, 2007 / hellonico

OpenWFEru on JRuby! Getting there …

Testing JRuby rev 4363 with OpenWFEru rev 1093 on OSX, with Java6 (1.6.0-dp). Ruby used was 1.8.6 (patch 0) which is known to have some threading problems.

All the jruby tests have -O -J-server options added. (Only those ones, compared to the vanilla jruby script)

1. Functional testing

jruby -Ilib:test test/ft_tests.rb

Finished in 63.312000000000005 seconds.
215 tests, 473 assertions, 0 failures, 0 errors

ruby -Ilib:test test/ft_tests.rb

Finished in 53.718509 seconds.
215 tests, 473 assertions, 0 failures, 0 errors

2. Quick in-memory testing

jruby -Ilib:test test/rake_qtest.rb

Finished in 75.07900000000001 seconds.
291 tests, 765 assertions, 1 failures, 0 errors

ruby -Ilib:test test/rake_qtest.rb

Finished in 64.828691 seconds.
291 tests, 770 assertions, 0 failures, 1 errors

3. Load testing

jruby -Ilib:test test/ft_26c_load.rb

Finished in 47.230000000000004 seconds.
1 tests, 1 assertions, 0 failures, 0 errors

ruby -Ilib:test test/ft_26c_load.rb

Finished in 21.641532 seconds.
1 tests, 1 assertions, 0 failures, 0 errors

4. Thread testing (experimental)

jruby -Ilib:test test/ft_26b_load.rb

(hanging) doesn’t end

ruby -Ilib:test test/ft_26b_load.rb

Finished in 3.658117 seconds.
1 tests, 1 assertions, 0 failures, 0 errors

5. Long tests (cron, scheduler and such)

jruby -Ilib:test test/rake_ltest.rb

Finished in 624.205 seconds.
45 tests, 89 assertions, 0 failures, 0 errors

ruby -Ilib:test test/rake_ltest.rb

Finished in 620.397724 seconds.
45 tests, 89 assertions, 1 failures, 0 errors

6. Conclusion

What this basically implies is that OpenWFEru on JRuby is almost there. Functional, Scheduling, and Engine testing all working fine. With about 99% test success.

The load test is a bit of a downside. Load performance of jruby is getting only half as fast, while it is almost on the par with cruby on the other test. But there has to be a way where this can be solved, and improved in the short term.

This is really cool. 2 months ago, the same tests results were completely different (deadlock, speed concerns…) Congratulations to both teams.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: