Quoting [EMAIL PROTECTED]:
Hi Stan!
Have you tried using the -mmap option when starting Squeak? I notice that
according to the squeakvm man page:
squeak uses a dynamic heap by default with the maximum size set to
75% of the available virtual memory or 1 gigabyte, whichever is
David T. Lewis wrote:
You are probably just growing your image to the point where the operating
system starts swapping. The image will appear to be unresponsive, but if
you interrupt it with altperiod, it will eventually wake up and return
control to you.
David, my image doesn't
Quoting [EMAIL PROTECTED]:
Hi Stan!
snipped large post
Hi John, not confusing- an excellent response, thanks.
With the memory option it also cruises on under Linux, until it freezes at
70
million objects.
While it's still loading vmstat shows:
procs ---memory--
Hi, I've been testing Squeak's ability to handle large amounts of data. This
snippet:
testArrayFilling
| startTime endTime iArray jArray kArray |
iArray := Array ofSize: 100.
1
to: 100
do: [:i |
jArray := Array
Hi Stan!
Have you tried using the -mmap option when starting Squeak? I notice that
according to the squeakvm man page:
squeak uses a dynamic heap by default with the maximum size set to
75% of the available virtual memory or 1 gigabyte, whichever is smaller.
Perhaps Windows doesn't have
