The reason for this difference in virtual memory size between the 32-bit and 64-bit version is that on the 64-bit version a 512MB range of virtual memory is reserved for generated code. This is only reserved virtual memory and is not all committed. Only the memory actually used by generated code will be committed, and whenever the amount of code shrinks parts can be uncommitted again This is done to ensure the the generated code is within a 2GB range on 64-bit as this makes it possible to use near call and jumps.
Regards, Søren On Mon, May 24, 2010 at 03:58, Richard Corsale <[email protected]>wrote: > I had the same thing with the 64-Bit build. It went away when I put it on a > 32-Bit... > > > > On Sun, May 23, 2010 at 9:05 PM, niknah <[email protected]> wrote: > >> I'd like to run v8cgi on a VPS which usually gives you a small bit of >> memory on a large computer. >> >> When I run a simple shell, press ctrl-z, the shell is using 600+ meg >> of virtual memory. Is there a way to reduce this? >> >> Nothing much else wrong with it, libv8.so is only 3meg, it starts up >> quickly. >> >> I'm using ubuntu 9.1 x64, compiling with... >> GCC_VERSION="44" scons library=shared arch=x64 >> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users > > > > > -- > If it seems too easy, it's probably foul. > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
