Hello Nathan, We are using Ruote and JRuby in a couple of projects. One of them is in production right now.
The first one, uses ruote-kit as the process API, so we wrap it with Trinidad[1] (an embedded Tomcat server, with NIO support, lifecycle extensions and easy daemonization) The second one, uses AMQP as an async API to interact with processes, so no ruote-kit is really needed, although it's a good way to visualize and manage our ruote environment, so we pretty much took the approach I've just mentioned above. It might be interesting to mention that, for performance reasons, we use the Java-AMQP driver instead of the Ruby one. As for the JVM side, just use (Open)JDK7 in order to benefit from the huge speed improvements InvokeDynamic offers. Moreover, you should put extra care on tuning your JVM and garbage collector properly[2]: it really makes a difference. The bloodiest side of the "JRuby way" is integrating with Java libraries, which we accomplish via JRuby's Maven/Bundler integration[3]. It works for us. If you want to know something more, feel free to ask us. Regards, //nando [1] https://github.com/trinidad/trinidad [2] http://java.sun.com/performance/reference/whitepapers/tuning.html http://blog.headius.com/2009/01/my-favorite-hotspot-jvm-flags.html http://java.sun.com/performance/jvmstat/visualgc.html [3] http://blog.mkristian.tk/ (lots of info about jruby-maven-plugin) https://github.com/torquebox/jruby-maven-plugins On 13 Nov, 01:32, Nathan <[email protected]> wrote: > Is anyone running ruote in production using JRuby? As ruote uses > threads, I was thinking JRuby might be a more natural env. for it than > MRI. > > Thanks, > > Nathan -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
