Re: Trying to reduce SBCL memory usage
- From: Christian Lynbech <christian@xxxxxxxx>
- Date: Sat, 05 May 2007 07:54:41 +0200
"Trastabuga" == Trastabuga <lispercat@xxxxxxxxx> writes:
Trastabuga> Is it ok for the lisp image to be so big?
Yes, this is normal. SBCL will *allocate* a huge amount of memory but
only *use* the appropriate fraaction of it. Other implementation does
the same thing. At least on Linux, you can allocate more memory than
you have as long you do not actually use too much, everything till run
fine. This is also sometimes referred to as "overcommit" in memory
allocation.
Why SBCL is handling its memory like that I am not entirely sure, but
I guess it has something to do with the layout of memory and what data
is stored where. The OS memory management system is quite clever and
will pull in only the stuff that is actually used.
------------------------+-----------------------------------------------------
Christian Lynbech | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
- petonic@xxxxxxx (Michael A. Petonic)
.
- References:
- Trying to reduce SBCL memory usage
- From: Trastabuga
- Trying to reduce SBCL memory usage
- Prev by Date: Re: How Lisp's Nested Notation Limits The Language's Utility
- Next by Date: Re: How to print result nice in LISP without the nil att end
- Previous by thread: Trying to reduce SBCL memory usage
- Next by thread: Evaluation of quote function
- Index(es):
Relevant Pages
|
