I don't think that my previous email was enough clear. My question is: What I have to do to get more dynamic space available?  Is it just needed to edit the parms.lisp file, changing the dynamic-space-end up to a higher value? Has anybody already tried that (increase the dynamic space up to 1GB, changing the defaults options) with a successful compilation results?

On 7/19/06, Peter Hertmuller <phertmuller@gmail.com> wrote:

>     Gen Boxed Unboxed LB   LUB  !move  Alloc  Waste   Trig    WP  GCs Mem-age
>    0: 128844     1    27     0    13 527686944 172768  2050840    0   1  0.0000

And this says that practically all of the memory was used by newly
allocated small objects. Which really shouldn't be happening: while
these objects are being allocated, garbage collections should be
triggered, which move some of them from the 0th generation to older


Is your application maybe disabling the GC or alternately disabling

No, the application does not disable the GC or interrupts. I've been trying to force the call to the gc by means of (sb-ext:gc). It didn't work.

I've downloaded the source code from CVS, and I've tried to increase the dynamic memory space changing the parms.lisp file under /src/compiler/x86/ folder (I've followed the recomedations made in an email sometime ago for an X86-64 machine). My machine has 2GB of RAM, so I've increased the memory figures up to 1GB (changing the dynamic-space-end from 512MB (x29000000) up to 1GB (x49000000), considering that the dynamic-space-starts at x09000000. This didn't work as well. I've got an error when the compiler fires the make-target-2.sh. Appears the error:

//doing warm init

mmap: wanted 1073741824 bytes at 0x9000000, actually mapped at 0x40182000

ensure_space: failed to validate 1073741824 bytes at 0x09000000

(hint: Try "ulimit -a"; maybe you should increase memory limits.)

Typing "ulimit -a" appears the following information (in a Xeon machine with 2GB RAM)

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited

The parms.lisp file is not enough documented and I'm not able to get a successful compilation.

Do you have any ideas about what I have to do to increase the dynamic space?


Juho Snellman