[Gcl-devel] SET-STARTING-HOLE-DIVISOR

[Camm Maguire]

Greetings!

2.6.10 has a significantly improved memory layout and fixnum handling.
Much work was also done on graceful oom handling encountered by some
acl2 jobs on 'lesser' machines.  The statically compiled maxpage
variable was replaced with a runtime probe of the maximum number of
pages that can be brk'ed at each image startup.  The upshot is that GCL
needed to scale the hole dynamically, so #'si::set-hole-size had to
become a noop.

You can 

1) safely ignore the error
2) remove the set-hole-size call and let gcl handle the memory, or
3) replace the call with si::set-starting-hole-divisor, which will set
the initial hole size as a fraction of the probed maxpages.

This is simply a performance tweak.  A generous hole lowers the starting
gc overhead.  GCL will try to optimize this by itself, but you can
change the initial placement if you want to.

Take care,
-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah