On 10 July 2013 13:41, Tudor Girba <tu...@tudorgirba.com> wrote:
> Wow!
>
> This is really exciting.
>
> Thanks a lot, Igor. I value this help even more knowing how you feel about
> the modification. Or maybe you changed your mind in the meantime? :)
>
No. It just a pain, knowing that it can do better, but to do it you have to
change how VM manages the memory, which is much more work than what i did.
I am not looking from position of "making customer happy", but "making
myself happy",
because apparently i am also using same VM and i want it to shine not
just from outside, but inside as well.
That's why i am grumbling :)
So, okay.. i ran following:
| objectQuantity objectSize objects fs |
objectQuantity := 1024.
objectSize := 1024*1024.
objects := Array new: objectQuantity.
fs := 'allocation.log' asFileReference ensureDeleted writeStream.
1 to: objectQuantity do: [ :index | objects at: index put: (ByteArray
new: objectSize).
fs nextPutAll: index asString; cr.
fs flush
].
and run it on windows, and it actually behaved quite well,
at 472 Mb allocated , i got a low-space warning popup. And no ugly crash.
(note it cannot be strictly 512Mb, because some space already taken by
image + jit + etc.. )
now, i set
AddressSpaceLimit=1024
in .ini file
and run the same again, and it stopped at 984 (megs allocated), again
showing low-space warning
(but it took a whiile to show it.. and image responding quite slow..
maybe because i run on virtual box
and it is more memory than i gave to boxed windows, so it forced to do
a lot of disk swapping.
so, it works.
--
Best regards,
Igor Stasenko.
