magma handle memory
Burella Juan M.
juan.burella at gmail.com
Mon Aug 6 19:43:39 UTC 2007
I need to do a massive migration to Magma. My approach is currently like
this: I'm loading the data from external files, then build a complex object
and commit it to a magma repository, and over again until the file ends.
While doing this, my image was growing at very high rates, approx. 200Mb and
taking several days, between 5 or 6. So, to see what's happening, I've done
some tests with toy objects, each one of them has 5 iVars. and each one has
another 5 iVars. This generates a tree of 19.556 objects
(5^0+5^1+5^2+5^3+5^4+5^5). Then I started to adding 50 of these "tree" (or
smock?) objects, by groups of 5. I tried to maintain the complexity of these
objects by adding "random" variable sized strings to the leafs and other
When this 50 are finalized, I've done:
self magmaSession stubOut: aCollection. "aCollection has 50 smock objects"
aCollection := nil.
self magmaSession finalizeOids.
But still the image is increasing its size. At beggining of the test the
image size (as reported from #vmParameterAt: 3) was approx. 60Mb and at the
end was approx. 89MB.
Any suggestions for reducing the growing of the image size?
Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Magma