From: Asher <asher@...>
Date: 2011-05-25T02:51:48+09:00
Subject: [ruby-core:36435] Re: GC thought

My understanding was that there are relatively major thread-safe issues all around?

I believe that doing this would require locking/unlocking every heap slot every time it's accessed� at that point, why stop the first thread at all?

From what little I know from having looked into the GC before, I thought that multi-threaded GC is a fairly standard option but not feasible here.

But I'm also interested to hear more from those in the know.

Asher

On May 24, 2011, at 10:57 AM, Roger Pack wrote:

> Hello all.
> Had a thought for improving ruby's GC the other day.
> 
> Currently it's
> 
> *stop world*
> mark
> sweep
> *start world*
> 
> suggestion:
> 
> *stop world*
> mark
> sweep a little bit
> *start world*
> finish sweep in another thread.
> 
> (Obviously there's be some ramifications, like having to add some
> locks here or there, and doing some thread joins, but hopefully that
> wouldn't cost too much cpu-wise).
> Thoughts?
> -roger-
>