From: Jeremy Tregunna <jtregunna@...>
Date: 2005-03-22T13:33:12+09:00
Subject: Re: GC performance (Re: RCR 296: Destructive methods return self)


On 21-Mar-05, at 10:52 PM, Navindra Umanee wrote:

> Glenn Parker <glenn.parker@comcast.net> wrote:
>> Oooo, pretty!  Seems like it might defeat the goal of optimizing 
>> things,
>> unless the reference counting could reduce the overall impact of 
>> garbage
>> collection.
>>
>> When I'm playing with simple algorithms, disabling garbage collection
>> seems to yield a guaranteed 20% speedup, even for relatively short 
>> tasks
>> (< 30 sec.).
>
> Interesting observation and benchmark!  It might be neat to have
> further details on how you are testing this.  Or is this measurement
> done on an actual app that you have deployed?
>
> I guess it might make sense for a Ruby app to disable GC and invoke it
> when really necessary in a speed-critical situation.

Or maybe it would be wiser to move to an incremental GC, where the 
overall impact of the GC is negligable.

> Cheers,
> Navin.

--
Jeremy Tregunna
jtregunna@blurgle.ca