I've noticed the same thing as well...

Does incremental GC get triggered based on the size of new space?  It
seems like incremental GC constantly thinks that it needs to run when
you allocate a huge object.  Looks like the big object has to make it
into old space before things starting working well again.

- Stephen

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org 
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On 
> Behalf Of Carlos Sarraute
> Sent: Wednesday, August 08, 2001 8:18 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: do I have to garbageCollect every time I create a 
> large object?
> 
> 
> Hello,
> 
> I have noticed something curious: after creating a very large 
> object (Array new: 25000000 which ocupies 100.000.000 bytes 
> of memory), everything gets very slow, and the SystemMonitor 
> indicates constant incremental garbage collections. It is 
> only after performing a full garbage collection (Smalltalk
> garbageCollect) that I can work again normally. My question 
> is: do I have to do "Smalltalk garbageCollect" every time I 
> create a large object? Or are there other ways to handle this 
> situation?
> 
> Thanks,
>  Carlos Sarraute
> 
> 
> 
> 
> 
>