It's bound to be the same. I encountered this quite extensively when using VSE on Win32. There were normally a couple of system DLL's that got plonked into the middle of it's address range and just moving those to one of the outer edges would mean the image could be started with a much bigger address space. Some would move without issues, some would just refuse to budge and some would appear to work until you actually called something in the offending dll :)

The simplest quick gain I could get was to use the Windows /3gb switch. This would give you an extra gb of contiguous memory and mean you could run an image just shy of 1gb. This increases to just under 2gb when you run it on a 64-bit machine. Even though the VM itself wasn't 64-bit, you still get the memory benefits.

From: Mariano Martinez Peck <marianopeck@gmail.com>
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Cc: CHRIS BAILEY <cpmbailey@btinternet.com>
Sent: Monday, 8 July 2013, 12:46
Subject: Re: [Pharo-users] More than 500MB for windows

I remember there was a thread where Andreas explains why the windows VM would not alloc more than 500 MB. I think it's quite similar if not the same to what Chris has said. If this is the case, MAYBE, depending on which dlls/plugins you use, you may be safe and alloc more??? Don't know...
I can search the email if you want. 

Cheers,


On Mon, Jul 8, 2013 at 8:33 AM, Usman Bhatti <usman.bhatti@gmail.com> wrote:
On Mon, Jul 8, 2013 at 1:26 PM, CHRIS BAILEY <cpmbailey@btinternet.com> wrote:
This is a standard problem on Windows whenever something tries to allocate contiguous memory due to the way it fragments your exe's memory with it's own dlls. I was able to get 1.4gb with some pretty nasty hacking of an exe once by rebasing the biggest offending dlls (it wasn't Pharo but the same principles should apply). You can find them using dependency walker. Be aware it can come with side effects as some really don't want to be moved, and as such I second Sven's OS comment ;-)

Tx for the hint. I'll first try image level optimizations before descending down to OS-level.
 


From: Usman Bhatti <usman.bhatti@gmail.com>
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Sent: Monday, 8 July 2013, 12:05
Subject: [Pharo-users] More than 500MB for windows

[I know there were some discussions on the topic and the topic of 64-bit VM but I'm not sure where we stand today].
I would like to know if we can allocate more than 500MB for pharo virtual machine in Windows? I am getting an "Out Of memory" msg and the following VM statistics when trying to parse a large application with Moose. Increasing the size would be the cheapest option (in terms of effort) before trying other optimizations.

tx

Inline image 1







--
Mariano
http://marianopeck.wordpress.com