On Wed, Dec 7, 2011 at 2:30 PM, Dmytrii Nagirniak <[email protected]> wrote:
> We also found that our hour-long cuke run would get in to some weird GC > fail-loop where it would OOM no matter how much memory you gave the JVM. > > Also also we had weirdness with the JDBC wrapper & ActiveRecord & > background tasks. > > Can you give some more details on this if you still remember those? Just to > be aware of. > Do you think it could have changed since then? They were specific to the JRuby / AR version we were using. Unless you're working in a legacy stack (JRuby 1.4, Rails 2.3.5) you won't hit them. The point was more that strange things can happen that don't happen to the majority of the community. Ruby/Rails' popularity means that issues are identified and fixed or worked around often. You will be reducing your available knowledge pool if you hit a JRuby specific issue, just as if you decided to deploy your stack on a less common operating system. However, JRuby is pretty mature and has a solid user base, certainly compared to JVM ports of other languages like Python. -- Michael Pearson -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
