> 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
ones.
Is your application maybe disabling the GC or alternately disabling
interrupts?
//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.)
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?
Peter
--
Juho Snellman