On Fri, Jun 08, 2007 at 02:07:35PM -0700, John M McIntosh wrote:
Ok, I build a new VM using these changes then poked about and wondered about the following compares as below.
Also did some tests, by altering mmap I ran the VM at the 3GB boundary, that seemed to work ok.
I then attempted to run it at the 1.5 GB boundary using a memory size of
641,732,608 at the 1.5GB boundary
The basic image (a 3.5 image) started at 20MB. I then allocated 450 mb of memory and did macro-benchmarks
| suck | suck := OrderedCollection new. suck add: (ByteArray new: 1024*1024*450). 100 timesRepeat: [ Smalltalk macroBenchmarks. suck add: (ByteArray new: 1024*1024*1). Transcript show: Smalltalk garbageCollectMost;cr. Transcript show: Smalltalk garbageCollect;cr].
However when young space approached, when over, inbetween, whatever the 2GB boundary the VM core dumped.
Hi John,
Thanks for the feedback. It's good that you've got a fairly repeatable failure scenario. When I did those changes, I was working on a 64 bit machine, and the Squeak heap gets allocated at e.g. 0x2b39e0c5a000, so I would not have been seeing the 2GB boundary on that machine. I guess I should go back to a 32 bit box and reproduce the problem there.
I might not get a chance to look at this further for a couple of weeks though. Right now my pet project is to see if I can get Areithfa Ffenestri working on unix.
Dave