On Tue, Dec 17, 2002 at 10:51:21AM +0100, Eric Marsden wrote: > I don't know anything specific about FreeBSD virtual servers, but can > try to give some general information that may help. I know that CMUCL > does work under User-Mode-Linux, which sounds like the equivalent of > FreeBSD virtual servers.
A FreeBSD virtual server running in a VMware instance is kinda like user-mode Linux; one running in a jail is like a chroot environment on steriods. So far, the virtual server providers I've found use jail, mainly because jail comes as part of FreeBSD but VMware is commercial software and unsupported on FreeBSD. > CMUCL doesn't _really_ allocate huge amounts of memory at startup: it > is only reserving a large amount of memory for possible future use. So > its "virtual size" is very large, but only around 17MB are resident > initially. You can reduce the virtual size by using the > -dynamic-space-size commandline option (try with 100 for example), and > by building a "small" core. Yup, I collected some numbers with top and these agree with you. Essentially, in a virtual server environment, the resource limits are such that CMUCL can't even start and my provider-to-be is unable to play the tuning game with me. Well, there are still CLisp and ThinLisp to check out... > this is only present in CMUCL for Debian/Linux (and I don't think that > it works any longer); it won't be useful for FreeBSD. Ok. Anyways I browsed thru the Debian source distribution of CMUCL and couldn't find the relevant code apart from the defswitch. The author says it's disabled; if the code is there, I can't see it. Meaning I'm unlikely to be able to hack on it. ;-) Thanks for the reply. Happy holidays. -- Ng Pheng Siong <[EMAIL PROTECTED]> * http://www.netmemetic.com
