Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!newsfeed.internetmci.com!howland.reston.ans.net!Germany.EU.net!news.maz.net!news.ppp.net!news.Hanse.DE!wavehh.hanse.de!cracauer
From: cracauer@wavehh.hanse.de (Martin Cracauer)
Subject: Re: CMU CL
Message-ID: <1996Jan17.145721.549@wavehh.hanse.de>
Organization: BSD User Group Hamburg
References: <4ddv3k$b9k@usenet.ucs.indiana.edu>
Date: Wed, 17 Jan 96 14:57:21 GMT
Lines: 29

schooler@silver.ucs.indiana.edu (lael schooler) writes:

>I was looking over the faq and saw that CMU CL requires only
>16 M of RAM to run. Has it changed from the 256 it used to
>require or is this a typo? 

Well, RAM is only for speed. I run CMU CL on 8 MB SPARCs regulary, no
problem, really. With 16 MB you can run the Common Lisp System iself
without or nearly without swapping, if the code your run doesn't
require much own memory. Any GUI for Common Lisp will be hard to use
with 16 MB.

I don't know where the 256 MB requirement note came from, but maybe
you mean an effect on the DEC Alpha. From the Unix platforms CMU CL
runs on, only the Alpha doesn't do lazy swap allocation by
default. CMU CL in fact *preserves* a lot of memory (that doesn't mean
it is *used*), about 250 MB (or was it 140?) and if you doesn't have
lazy allocation, you need to have that much virtual memory.

This has nothing to do with RAM requirements. You can change your OSF
machine to do lazy swap allocation with `rm /sbin/swapdefaul`.

Happy Hacking
	Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@wavehh.hanse.de>  -  Fax +49 40 522 85 36
 BSD User Group Hamburg, Germany   -   No NeXTMail anymore, please.
 Copyright 1995. Redistribution via Microsoft Network is prohibited
