Hi Timothy,

> On Oct 17, 2021, at 8:41 AM, gettimothy via Squeak-dev <squeak-dev at lists.squeakfoundation.org> wrote:
> 
> 
> Hi Folks,
> 
> 
> I am thinking about the result of parsing that 73Gb xml file and storing many of its elements in squeak as live objects.
> 
> Assuming an ~1:1 relationship betwen that file and the resultant image, can Squeak handle that?
> 
> Can I tell squeak to "SmalltalkImage getLarge:73Gb"  ? 
> 
> 
> I think It would be a fun experiment if this possible.
> 
> thx in advance.

In theory there should be no problem other than a rather sedate snapshot and start up time.  If your machine has enough ram and disc Spur will save and restore that size of image.  You may find that increasing the size of new space/eden to 128/256/512mb, increasing the old space segment size to 1gb, and especially changing the growth to size GC ratio, decreases build time substantially.

About Squeak is your friend.  Under vm parameters you’ll find info on sizes and rooting around you’ll find the levers for setting these sizes through vmParameterAt:put:.  See parameters 25, 45, & 55. #25 is badly described.  It is actually the minimum old space segment size.  Setting this to eg 1gb means a lot less segments to traverse than the default 16mb.

I’d be interested to see the vm stats at the end of a build. Those will help you tune and find out how much time is being spent in GC.

_,,,^..^,,,_ (phone)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20211017/d1594b5a/attachment.html>