Pharo images should be smaller than 3.9.1 images since code was
removed. The Pharo image 10061 that I build from the very beginning
through the update stream is 14.2 MB after I did the following cleanup
(can you try if it helps? I guess MC holds versions in its cache).
Squeak 3.9.1 final is 15.6 MB. I don't understand how you get images
that are smaller than 10MB?
Adrian
RequiredSelectors initialize.
ProvidedSelectors initialize.
LocalSends initialize.
Utilities cleanseOtherworldlySteppers.
Smalltalk organization removeEmptyCategories.
SystemBrowser removeObsolete.
TheWorldMenu removeObsolete.
AppRegistry removeObsolete.
SystemNavigation default obsoleteBehaviors.
MCFileBasedRepository flushAllCaches.
MCDefinition clearInstances.
Symbol compactSymbolTable.
Set rehashAllSets.
Smalltalk garbageCollect.
On Aug 20, 2008, at 14:54 , Damien Cassou wrote:
Hi,
according to stats I did about Squeak and Pharo
(http://damiencassou.dabbledb.com/publish/dev-imagesdownloads), Pharo
images are always bigger than Squeak images. This does not seem to be
related to the dev-images themselves because the latest base Pharo
image is bigger (8.79 MB) than Squeak 3.10.2 (7.1MB) and Squeak 3.9.1
(also 7.1MB).
Is there any method to call to clean the image? Would be interesting
to systematically clean the releases you build.
Bye
--
Damien Cassou
Peter von der Ahé: «I'm beginning to see why Gilad wished us good
luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
