[Gc] Re: Partially scanning a VM's call stack
ludo at gnu.org
Wed Aug 19 06:43:25 PDT 2009
Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> writes:
> I must say that I have experienced an important performance increase
> (this was long time ago) by telling the garbage collector explicitely
> which regions of the interpreter stack are active. The reason is that
> lisp code can get depply recursive pretty fast, filling the stack with
> lots of data that should then be quickly discarded. Without code to
> mark that region of the stack as no longer use, a lot more data is
> retained. The same will probably happen on any interpreter that uses a
> separate structure to store the stack of the interpreted code.
Fortunately Scheme's RnRS require proper tail-call optimization. :-)
But I get your point.
More information about the Gc