> On 13 Sep 2016, at 18:54, Vitor Medina Cruz <vitormc...@gmail.com> wrote:
>
> I understand. I thought it did more stuff, like remove necessary development
> tools or executing processes,
It does call #cleanUpForRelease, but this we call at *every* update on the CI,
too. This calls the #cleanUp method of all classes
and does some more (rehashing all dictionaries, restarting all? methods holding
on to blocks…).
> I don't know, but considering its implementation it should affect only the
> image size, right?
>
Yes. Of course right now Cog is not compacting the somewhat empty allocated
memory regions, so e.g. the
47 MB image should be around 15 MB empty space and the cleanup will not shrink
it.
But when this is fixed, you should see a change. A saved image is too a large
extend methods and literals they
point to (especially for things like Tutorials). In the past the normal image
was ca. 25MB, while the shrieked one
after cleanup for deployment maybe 15? I do not remember.
But that was already a bit of “moored law” time ago ;-)
Marcus
