From: matz@... (Yukihiro Matsumoto)
Date: 2003-02-21T09:17:47+09:00
Subject: Re: String#+ operatorbroken?

Hi,

In message "Re: String#+ operatorbroken?"
    on 03/02/21, Jim Freeze <jim@freeze.org> writes:
|> |Well I think we found a weak spot in the new GC.
|> Probably.  Could you see what if "1.8" around line 307 in gc.c
|> 
|>     heap_slots *= 1.8;
|> 
|> to something like 1.4 or 1.2?
| 
| It still grows with 1.2, but not as fast.
| After 1 minute, it had reached 200MB.

Sorry, I was looking at wrong place.  The current GC increases
malloc_limit too radically.  I think I fixed the problem.  It consumes
less then 30MB.  But I have no idea why it's still slower than 1.6.8
after the fix.

							matz.