From: Yukihiro Matsumoto <matz@...>
Date: 2009-12-12T00:08:40+09:00
Subject: [ruby-core:27145] Re: Ruby's GC

Hi,

In message "Re: [ruby-core:27144] Re: Ruby's GC"
    on Fri, 11 Dec 2009 23:57:24 +0900, Rick DeNatale <rick.denatale@gmail.com> writes:

|I suspect that the write barrier can be implemented rather efficiently
|depending on how memory layout is done. You need to be able to
|efficiently distinguish between mutations to references in old objects
|(which need to be remembered) and mutations in new objects, which
|don't.
|
|One interesting problem, is what effect a copying GC would have on the
|API to C extensions, since object addresses would no longer be stable
|over time.

Non conservative GC would damage almost all C extensions for Ruby.
I don't think it's acceptable for CRuby.

Regarding of copying GC, one thing I have interest is how its
copy-on-write unfriendliness effect the performance under Web
environment.

							matz.