On 28 Feb 2012, at 23:25, ted f.a. van gaalen wrote:
it's about image size.
Currently, Pharo 1.3-13315 at my 4 Gigabyte Debian amd64 Linux machine reports
memory 75,392,160 bytes old 61,370,144 bytes (81.4%) young 2,169,692 bytes (2.9000000000000004%) used 63,539,836 bytes (84.30000000000001%) free 11,852,324 bytes (15.700000000000001%)
(nothing peculiar added, just the Seaside package and a few classes of my own. )
So, if i understand this well I have only 11,8 megabytes to play with?
To begin with: why is only 75 megabyte available in Pharo (or Squeak as well) when there is 4 gigabyte physical memory available on my machine??
You are interpreting this wrongly: total memory allocation of the heap did not yet grow beyond 75Mb because you still have 11Mb free, so there was not need for it. See this thread: http://forum.world.st/Big-Image-Tests-td4188045.html#a4188548 Although you cannot allocate much more than 1Gb, that is already more than enough for a lot of purposes. Of course, 64-bit VMs / Smalltalk images would be helpful in growing even larger, there seems to be some progress there. Sven