Ng Pheng Siong <ngps@netmemetic.com> wrote:
+---------------
| According to Johannes Groedem  <johs+n@ifi.uio.no>:
| > * ngps@netmemetic.com (Ng Pheng Siong):
| > > Two FreeBSD-based ones I spoke to balked at CMUCL's startup memory
| > > requirement.
| > 
| > What?  6MB?  I thought people could afford this much these days.
| 
|   PID USERNAME  PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
|   510 ngps        2   0  1269M  5992K select   0:00  0.00%  0.00% lisp
|                          ^^^^^
| CMUCL wouldn't start on their test-drive boxens' default configs.
| (These are FreeBSD jail-based virtual server environments.)
+---------------

Hmmm... There may be a problem with the FreeBSD "jail", then, or maybe
it's just that their config is too restrictive. While it's true that
CMUCL *maps* that much at startup, it doesn't actually touch much more
than the startup code plus the bits of the saved image that you really
use, hence that modest ~6M "resident set size" you see there -- plus,
of course, any additional space you allocate (times 2, after the next GC).

I run a persistent web application server in CMUCL quite handily under
FreeBSD on several machines, from a speedy mid-sized server down to a
fairly small (48MB), slow (133MHz) laptop. FreeBSD handles CMUCL's VM
demands quite handily, when you let it...


-Rob

-----
Rob Warnock, PP-ASEL-IA		<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607