Thanks for you answers,
it seems that there is a problem with sbcl and linux 64-bit.
I noticed that this problems does not appear on my 32-bit systems only on the
64-bit systems.
If I start sbcl with --dynamic-space-size there is no effect by allocating more
memory than specified - therefor I
IE> As I recall, when allocating space in the heap for new objects, SBCL
will periodically
IE> ask the OS for more heap memory. Even if the objects are garbage
collected later,
IE> the allocated memory will remain (SBCL never releases heap memory back
to the
IE> OS even if it isn't using mo
I'm not sure if Elephant will play nicely with Berkeley DB 4.8 yet - we should
probably fix this. For now, however, you can ignore the db_deadlock setting in
my-config as it is not strictly required as of 4.7.
Ian
On Mar 5, 2010, at 12:49 AM, Nicolas Neuss wrote:
> Hello,
>
> I would like to
Hi Lukas,
How are you defining 'memory not released'? Is this a measure of the Lisp heap
or the OS footprint?
As I recall, when allocating space in the heap for new objects, SBCL will
periodically ask the OS for more heap memory. Even if the objects are garbage
collected later, the allocated
Hello,
I would like to start using Elephant. Unfortunately, I do not know much
about the Berkeley database system, so I am stuck just at the beginning.
I would like to use the Berkeley libraries which come with my
Debian/Lenny (which is version 4.8), and cannot find the db_deadlock
binary there
