magma handle memory

[Burella Juan M.]

Hi Chris, sorry for the delayed reply;
I'm going to test the sample trying to aproximate the depth of my real
objects, which could be of 20 levels per object, having 12,000 of them (if
you remember from the first mail I´m building these objects one by one
collecting the data from a file). Under this scenario, the image growth
reach 200Mbytes and it became unstable, so I have to shutdown the image and
restart again all the process. I cannot reproduce this scenario with the
samples I´ve sent to you, and I think that´s the reason why you haven´t seen
the problem we're experimenting here.
Now we´re going to test the sample with the numbers above, and if I can
reproduce the behavoir I´ll send to you the results.

Thanks
Juan Matías.


On 8/10/07, Chris Muller <asqueaker at gmail.com> wrote:
>
> Juan, I spent some time running your neat test case but it didn't show
> me any unreasonable growth.  So I then went back to the output you
> posted and looked at it in detail.
>
> Regarding the output you pasted in your previous message:
>
> =======================================
> Creating magma repository
> Opening magma session
> Image size before creating magma collection: 69851252
> Creating magma collection at MagmaMemoryTest
> --Iteration: 1..5:
> Image size BEFORE creating test object: 69851252
> Creating test objects...
> Image size AFTER creating test object: 69851252
> Saving 5 next objects from collection to magma collection...
> Image size BEFORE Magma cleaning: 85098444
> Image size AFTER Magma cleaning: 82623944
> --Iteration: 6..10:
> Image size BEFORE creating test object: 82623944
> Creating test objects...
> Image size AFTER creating test object: 82623944
> Saving 5 next objects from collection to magma collection...
> Image size BEFORE Magma cleaning: 106407888
> Image size AFTER Magma cleaning: 83066628
>    ...
> --Iteration: 46..50:
> Image size BEFORE creating test object: 85159312
> Creating test objects...
> Image size AFTER creating test object: 85159312
> Saving 5 next objects from collection to magma collection...
> Image size BEFORE Magma cleaning: 108594588
> Image size AFTER Magma cleaning: 85183668
> ==================================
>
> End of memory at the beginning shows:
>
> --Iteration: 6..10:
> Image size BEFORE creating test object: 82623944
>
> at the end:
>
> Image size AFTER Magma cleaning: 85183668
>
> 85183668 -82623944      =  2559724
>
> So, end-of-memory, through all of the bulk-load operations, needed to
> advance only 2.5MB through dynamic allocation, etc.  Is this
> unreasonable?
>
> Further, your output indicates there was only initial mild growth from
> the first three iterations.  Then, beginning with --Iteration:
> 16..20:, it stayed relatively static at roughly 85MB.
>
> Am I missing something?
>
> Regards,
> Chris
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/magma/attachments/20070815/32010a4a/attachment.htm