Okey so I have found the Class instance that was holding onto the data. I
can now save my image after a parsing without tripling its size.
But the VM's memory footprint (according to Windows task manager) does not
falls back to normal after a parse. My guess is that now that the VM was
allocated m
On 09 Apr 2014, at 18:01, Thomas Bany wrote:
> Thanks !
>
> That's exactly what I was looking for. There is a compare method I dont quite
> understand but I think I found what is going on.
>
> I failed to grasp that an Array reply to #sizeInMemory with it's own size,
> without the sizes of i
Thanks !
That's exactly what I was looking for. There is a compare method I dont
quite understand but I think I found what is going on.
I failed to grasp that an Array reply to #sizeInMemory with it's own size,
without the sizes of its references. A single position object weight 96
bytes, which m
Hi Thomas,
Fixing memory consumption problems is hard, but important: memory efficient
code is automatically faster in the long run as well.
Your issue sounds serious. However, I would start by trying to figure out what
is happening at your coding level: somehow you (or something you use) must
I meant a single array weight something like 300Kb with the 32 of them
weighting arround 10Mb.
I tried to look closely at the way the memory (with
VirtualMachine>#memoryEnd) was incrementing and it follows this pattern:
- The memory costly function is defenitly the one storing my position
a
Your calculation seem to be off.
32 * 86400 objects = 2.8 million objects. A shortint = 4 bytes, making 10.6 MB
Everything else (except value objects) is larger.
Stephan
Hi,
My app is a parser/filter for binary files, that produces a bunch of ascii
files.
At the begining of the parsing, the filtering step involves the storage of
the positions of 32 objects, each second for a whole day. So that's 32
Arrays with 86400 elements each.
During this step, the memory us
