Smalltalk - Re: [Pharo-dev] Large images reasons [WAS] Re: Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower

Smalltalk › Pharo › Pharo Smalltalk Users

Re: [Pharo-dev] Large images reasons [WAS] Re: Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower

Posted by philippeback on Aug 01, 2013; 9:18am
URL: https://forum.world.st/Large-images-reasons-WAS-Re-Pharo-2-0-with-Seaside-DBXTalk-GlorpDBX-Magritte-3-TWBS-is-getting-slower-tp4701743p4701794.html

This trimmed a couple of megs indeed.

Then I did an ImageCleaner cleanUpForRelease.

and saved.

But nothing terrific as the size continues to grow.

Need to see where those MorphExtensions are coming from...

Phil

On Thu, Aug 1, 2013 at 9:33 AM, Marcus Denker <[hidden email]> wrote:

On Aug 1, 2013, at 8:56 AM, Stéphane Ducasse <[hidden email]> wrote:

> since years marcus is telling that MC storing ancestor information is doomed but we do not have something to really replace it.
>

This is yet another thing.

Monticello keep all history data of all package in image, this is not a cache. When you delete it, your package loses
it's history and you can not merge anymore.

MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ].

We did that on Pharo2 release and it saved 8MB (nearly a third of the image).

Marcus