On Sun, Jan 16, 2011 at 8:21 AM, Julien Schmurfy <schmurfy / gmail.com> wrote:
> As for jruby one of the problems is that it is another virtual machine
> and I may experience the same differences that i do with 1.8.7 (and it
> was not 1.9 compatible last time I checked so no Fibers either) but the
> main problem is we use eventmachine and while it is nice that the gem
> itself implements three versions (native, ruby, jjruby) they are all
> differents so... useless.
> Last time i tried to run my code under jruby there was so many problems
> I just gave up.

If it was simply 1.9 support holding you back with JRuby, you may want
to try JRuby 1.6.0.RC1, which shipped greatly-improved Ruby 1.9.2
compatibility. Not perfect yet, I'm sure, but far better than it used
to be.

But yes, if your leak is likely in an MRI-specific library, like EM,
profiling on JRuby probably won't tell you much (and JRuby might not
exhibit the problem at all). I sympathize.

- Charlie