On 16 Feb 2017, at 16:22, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 16 Feb 2017, at 16:16, denker <marcus.denker@inria.fr> wrote:
No,
Our image is not 47 MB⦠more like 28.
My understanding is: -> Cog works with âpagesâ (is that the term?) of memory. -> if a page is empty, it gets cleaned up and does not cost space when saving. -> if there is some object still allocated, the whole page will be saved (partly empty)
Not sure if that is completely right, but it explains why the image with lots of objects allocated new can shrink again, while the 47MB never shrinks, even though the image for sure is much smaller.
=> what is missing is a âcleanupâ phase that sweeps together all the half-empty pages.
What is fun is that we now ship a 47MB image and nobody ever complains. (or even asks)
Yeah, that proves it is not such a big deal, today. But still, we have to fix this discrepancy between 28 and 47.
As I tried to explain: the VM is missing a âcondenserâ that cleans up half allocated pages.
Is the 'release cleanup' done on this image each time ?
Yes. Marcus