On 12/18/05, Brad Beveridge <[EMAIL PROTECTED]> wrote: > Very nice. On my Linux x86 box, a freshly started SBCL core dump is > 26MB, which compressesd with bz2 down to about 6Mb. > Is it possible to optimise the size of the save core at all? I've > heard the term "tree-shaker" mentioned, I presume this removes all > functions that aren't called from the image? This must also remove > almost all possibility of further extending an image once deployed, > but for many applications this isn't a problem. > > Is it possible to write a portible common-lisp tree-shaking algorithm? > Yes, to reduce the size of a core, parts have to be selectively removed from the image. I fear, this is very implementation specific. But as you say, SBCL cores compress nicely, so for the delivery of most applications, this should not be a too big problem. And if you want to deploy several small utilities, nothing speaks against putting them all in the same core and just modifiy the startup-script to start the different utilities.
Peter _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
