Hello, Sorry for the late answer.
I think there are multiple problems… 1) slowness. This is strange that unloading packages is so slow. This looks like a bug to me. 2) image size in Pharo5: We have a bug right now that images *never* shrink. This means that if you save an image once with 80MB, even if the GC cleans up, the saved image stays 80MB. We should fix both…. > On 25 Jan 2016, at 13:32, Maximiliano Tabacman via Pharo-users > <pharo-users@lists.pharo.org> wrote: > > > From: Maximiliano Tabacman <mtabac...@yahoo.com> > Subject: Image Cleaner no longer useful? > Date: 25 January 2016 at 13:31:28 GMT+1 > To: "pharo-users@lists.pharo.org" <pharo-users@lists.pharo.org> > Reply-To: Maximiliano Tabacman <mtabac...@yahoo.com> > > > Hi, and sorry if this has already been discussed. > > In Pharo 3, I used to be able to do: > > ImageCleaner cleanUpForProduction > > and that would correctly remove a lot of unneeded code in the image when > preparing for a productive release. > Then I would save the cleaned image, and since it had been cleaned, it would > be smaller than the original development image (say from 60 mb to 25 mb). > This process would take about 2-3 minutes. > > Then, in Pharo 4 it seems some changes were made here, since the same process > took a lot more, like 20 minutes. > > When I first tried Pharo 5, I was happy to see that it was again down to 2-3 > minutes. > > And here comes my question... > Why is it that since some 2 months ago (maybe more), the Pharo 5 images once > again require like 20 minutes to complete the cleanUpForProduction process? > > Also, and this is the most relevant to me, it no longer reduces the image > size. > So if I want to release a Pharo 5 version based on the latest images, I would > be shipping a product that is more than twice the size of previous public > versions of my software! > > Thanks for any insights into this. If it is a known bug, I would like to know > if there is any workaround, or alternative objects that I should be using for > the process. > Also, if it would help for me to run any tests in particular to share and > help in fixing this, please let me know. > >
