Hi, I'm checking out FreeBSD virtual server providers, with the intention to host a CMUCL-based webapp.
A FreeBSD virtual server is typically an instance of a FreeBSD "jail" set up to be a complete FreeBSD environment; multiple such instances run on one physical host. Alternatively, the FreeBSD virtual server may be a "real" (or still jailed) FreeBSD environment running in a VMware instance; again multiple such instances, plus possibly instances of Linux, Windows and whatnot, run on one physical host. This is a low-cost alternative to server colocation. Anyhow, on one such provider's test boxen, CMUCL (18d, from Ports) segfaults upon startup. It is likely due to CMUCL allocating gobs of memory at startup. On my desktop, top reports thusly: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 511 ngps 2 0 1268M 29168K select 0:04 21.44% 10.25% lisp This is right after loading PAserve, USQL, etc., but before running my application, which I haven't profiled. ;-\ Looking around the archives, there is a "-lazy" command line switch meant to work around Linux VM weaknesses. Will this option help me in my situation? Does it take a lot of effort to make "-lazy" work on FreeBSD? Any other suggestion? TIA and season's greetings. -- Ng Pheng Siong <[EMAIL PROTECTED]> * http://www.netmemetic.com
