From: matz@... (Yukihiro Matsumoto)
Date: 2002-09-04T12:01:10+09:00
Subject: Re: Best GC for Ruby?

Hi,

In message "Re: Best GC for Ruby?"
    on 02/09/04, Dan Sugalski <dan@sidhe.org> writes:

|>Generational GC performs quite well if there are bunch of live
|>objects.  But when we implemented the generational GC for Ruby, the
|>write barrier cost wasn't trivial.  As a result, we lost performance
|>for avarage cases.  Probably more efficient write barrier such as card
|>marking may help.  We will try again someday.
|
|Bummer--I'd hoped you had a good solution to my existing problem. :) 

Life is not that easy as always. ;-)

|The exposure of the internals, even partially, to extensions written 
|in C also seem to complicate things.

To make things easy, we put all touched (i.e. internal revealed) C
data into remembered set.

							matz.