DISQUS

Oracle AppsLab: Mix, JRuby on Rails, Small Teams, Agile, and it’s Effects on the World

  • Charles O Nutter · 1 year ago
    JRuby, not jRuby. Thanks for the kind words and congratulations on a great project. I agree the future is bright for JRuby. I hope we'll have opportunities to work together...in the open...in the future.
  • Wes Maldonado · 1 year ago
    How did you manage the development cycle when you went from using MRI to JRuby? Do you still use MRI for development and then package for deployment with JRuby?
  • Rich Manalang · 1 year ago
    Charles... thx for the correction... I'm so used to working with jQuery that I treat any project with a "j" in front as "j<fill in="in" the="the" blank.="blank."></fill>
  • Rich Manalang · 1 year ago
    Wes, yes, we still dev on MRI, then test and deploy on JRuby. So, far it's working pretty well.
  • ed · 1 year ago
    Were you going against JRuby 1.0 or 1.1? If 1.1, using the JIT mode?
  • Rich Manalang · 1 year ago
    Ed, we took a snapshot of 1.1 after the performance patches went in. We're running in interpreted mode.
  • WildKid · 1 year ago
    Really good and really interesting post. I expect (and other readers maybe :)) new useful posts from you!
    Good luck and successes in blogging!
  • Artem Vasiliev · 1 year ago
    Can you post 'rake stat' results please? Just interesting..
  • Floyd · 1 year ago
    Rich,

    This is a great "war story" about a small team focusing on a single effort over a short period of time to achieve a huge positive impact. Thanks for sharing. We need more success stories like this.
  • Ben Curren · 1 year ago
    Would you share some of the configuration details for the server? For example, how many Rails instances did you setup in the RailsServlet? What flags did you pass to the JVM to improve performance? Any other tricks or insight would be greatly helpful. We are launching a product in mid January and are starting to go through the same performance tuning you are speaking of here.
  • Rich Manalang · 1 year ago
    Ben, we're running goldspike with the defaults. We're not even running under JNDI yet :-)

    The only real performance tweak we did was to use JRuby trunk :-). The other part is to off-load our static content to a web server that's more efficient at handling static content -- in our case, Apache -- we could have gone with Nginx, but Apache comes is already enabled with Oracle AppServer, so we used that.

    I'm sure there are tons of other performance options we can enable, but for now, we're running pretty smoothly.

    However, I was chatting with one of the JRuby devs today and it looks like they just found a big mem leak related to HTTP POST requests... so, you may want to wait for the official 1.1 release of JRuby.

    Rich