From: Florian Gilcher <flo@...>
Date: 2013-01-14T16:12:14+09:00
Subject: Re: Garbage Collection and Fibers


On Jan 14, 2013, at 1:43 AM, Na Na <lists@ruby-forum.com> wrote:

> Aha.  I realised that running it in a separate thread or fiber would
> mean it would miss some objects, but I was thinking that would mean it
> may not deallocate them when it should, which I didn't care so much
> about.  I didn't think that it might cause some to be deallocated when
> they shouldn't!
> 
> So I suppose my options are:
> * Call GC only when suits me, and put up with the slowness as a part of
> life
> * Reduce the number of objects I use
> * Tweak the GC settings so that it's needed to be called less frequently
> (but I suspect this will just postpone my issues)
> * Try ruby 2.0's GC
> * Use something other than ruby for my app (nowhere near an ideal
> option!)

Don't forget option X: If you don't need extensions that are fundamentally
incompatible, have a look at running the whole thing on JRuby. It uses the
JVMs GC, which is much better and doesn't suffer from stop-the-world 
issues as much. It is also very compatible with MRI.

Regards,
Florian