Re: SBCL performance on OS X

On Tue, 06 Dec 2005 10:02:15 +0000, Christophe Rhodes wrote:
>
> Possibly the most straightforward way of achieving this is to shrink
> the available heap size. This is easy to do for SBCL: simply change
> the parameters in src/compiler/ppc/parms.lisp and recompile.
>

Thanks very much for taking the time to reply with all this useful
information Christophe! I had been assuming that SBCL used a single GC
over all platforms. Things begin to make a lot more sense now.

Your comment above made me wonder if there's any fundamental reason nobody
has added a maximum-heap-size command-line switch to SBCL. Perhaps it's
just lack of time and/or interest? If that's the case I might have a go
at doing it myself.

Thanks again and best wishes,
Bill.
.

Relevant Pages

  • Re: memory problems
    ... If you are running out of heap, ... being bitten by the conservativism of the GC. ... For future advice on SBCL, I'd really recommend the sbcl-help mailing ... mailing lists (and posts like this without SBCL in the Subject are ...
    (comp.lang.lisp)
  • heap size exhausted in SBCL
    ... No backtrace shows up in SLIME, and I have to kill the sbcl process ... would like to analyze and solve this problem, but the fact that SBCL ... could this be SBCL detecting that UMFPACK exhausted the heap, ... management). ...
    (comp.lang.lisp)
  • Re: memory problems
    ... I will start a new discussion on the SBCL mailing lisp as advised, ... called several times while memory increases, but it looks like it is ... If you are running out of heap, ...
    (comp.lang.lisp)
  • Re: error message from SBCL Windows
    ... This is some kind of memory corruption, ... That could be either due to buggy foreign code, ... or an SBCL bug. ... There were frequent reports with heap ...
    (comp.lang.lisp)
  • Re: error message from SBCL Windows
    ... This is some kind of memory corruption, ... That could be either due to buggy foreign code, ... or an SBCL bug. ... There were frequent reports with heap ...
    (comp.lang.lisp)