30Mb image growth from loading VMMaker?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

30Mb image growth from loading VMMaker?

timrowledge
I've just noticed that the latest-from-jenkins image that I added VMMaker to this morning is 30Mb bigger than when it started. That seems a little excessive. There certainly isn't 30Mb worth of code involved.

SpaceTally says there is 29Mb of ByteStrings in the image, which seems rather a lot. In fact, I'll just attach the space report - it really is a bit alarming




tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: YVR: Branch to Vancouver





STspace.text1 (32K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 30Mb image growth from loading VMMaker?

Eliot Miranda-2


On Mon, Mar 25, 2013 at 7:46 PM, tim Rowledge <[hidden email]> wrote:
I've just noticed that the latest-from-jenkins image that I added VMMaker to this morning is 30Mb bigger than when it started. That seems a little excessive. There certainly isn't 30Mb worth of code involved.

SpaceTally says there is 29Mb of ByteStrings in the image, which seems rather a lot. In fact, I'll just attach the space report - it really is a bit alarming

I think you'll trace it back to Monticello state.  Try flushing caches and see what happens.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: YVR: Branch to Vancouver








--
best,
Eliot


Reply | Threaded
Open this post in threaded view
|

Re: 30Mb image growth from loading VMMaker?

David T. Lewis
On Mon, Mar 25, 2013 at 10:44:18PM -0700, Eliot Miranda wrote:

> On Mon, Mar 25, 2013 at 7:46 PM, tim Rowledge <[hidden email]> wrote:
>
> > I've just noticed that the latest-from-jenkins image that I added VMMaker
> > to this morning is 30Mb bigger than when it started. That seems a little
> > excessive. There certainly isn't 30Mb worth of code involved.
> >
> > SpaceTally says there is 29Mb of ByteStrings in the image, which seems
> > rather a lot. In fact, I'll just attach the space report - it really is a
> > bit alarming
> >
>
> I think you'll trace it back to Monticello state.  Try flushing caches and
> see what happens.
>

See senders of #flushAllCaches. Mainly it's this one:

  MCFileBasedRepository flushAllCaches.
  Smalltalk garbageCollect.

Dave


Reply | Threaded
Open this post in threaded view
|

Re: 30Mb image growth from loading VMMaker?

timrowledge

On 26-03-2013, at 4:48 AM, David T. Lewis <[hidden email]> wrote:

> On Mon, Mar 25, 2013 at 10:44:18PM -0700, Eliot Miranda wrote:
>> On Mon, Mar 25, 2013 at 7:46 PM, tim Rowledge <[hidden email]> wrote:
>>
>>> I've just noticed that the latest-from-jenkins image that I added VMMaker
>>> to this morning is 30Mb bigger than when it started. That seems a little
>>> excessive. There certainly isn't 30Mb worth of code involved.
>>>
>>> SpaceTally says there is 29Mb of ByteStrings in the image, which seems
>>> rather a lot. In fact, I'll just attach the space report - it really is a
>>> bit alarming
>>>
>>
>> I think you'll trace it back to Monticello state.  Try flushing caches and
>> see what happens.
>>
>
> See senders of #flushAllCaches. Mainly it's this one:
>
>  MCFileBasedRepository flushAllCaches.
>  Smalltalk garbageCollect.

Yup, that cuts 28Mb out. Seems like an awful lot of stuff to cache in-image.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Not enough sense to come in out of the rain.