3 ms·
The following data is for standalone executables (modulo things like libc and libm that most Linux executables depend on) Columns are: - apparent size (I run
by aidenn0 6y ago
The following data is for standalone executables (modulo things like libc and libm that most Linux executables depend on)
Columns are:
- apparent size (I run FS compression so the actual on-disk size is nearly the same between the compressed and uncompressed)
- Executable name: $IMPLEMENTATION.{big|compress} implementation here is either SBCL or CCL. "Big" means I load the drakma library before saving the image (which pulls in things like unicode tables). "compress" means I attempt to enable image compression; the numbers make it looks my system's CCL does not support compression.
- Mean time to run a program that quits immediately as a startup time proxy; sbcl pays a big penalty for compression as without compression it just MMAPs the image in so doesn't ever load most of the image when you quit immediately.
/bin/true is included for a minimal "fast and tiny C program" as a comparison.
31K /bin/true 85% .0004
43M sbcl 99% .0036
29M ccl 93% .0053
58M sbcl.big 99% .0049
14M sbcl.compress 99% .2012
44M ccl.big 95% .0071
44M ccl.compress 95% .0071
- nonameiguess 6y ago/bin/true will still forever irk me: https://twitter.com/rob_pike/status/966896123548872705 https://twitter.com/rob_pike/status/966896123548872705
- aidenn0 6y agoI should also comment that ECL makes very compact binaries, and the runtime, which is a dynamic dependency is a single digit number of megabytes. The start up time suffers though; on the order of half a second.