3 ms·
This doesn't include ceramic, but: I did a benchmark of executable image sizes and startup times for the popular open-source implementations[1] it depends on c
by aidenn0 11y ago
This doesn't include ceramic, but:
I did a benchmark of executable image sizes and startup times for the popular open-source implementations[1] it depends on cl-launch since asdf:program-op was still experimental at the time.
A few points I discovered:
SBCL and CCL are neck-on-neck for startup time; very slightly longer than a hello-world in python, but much faster than any python script that has to do any significant importing.
SBCL has by far the largest image size overhead ~80MB for "hello world". It has an option to compress the image with zlib, but that is a big impact on image startup time. I did a proof of concept of an lz4hc image compressor, and it made for acceptable startup times while taking the overhead down to under 30MB. Someone else turned this into a real patch, and it is waiting to be merged.
CCL's image size is about 1/2 that of sbcl.
ECL has, by far, the smallest image size, even including the DLL (3.2MB for a lisp runtime is tiny!). However, it has a startup time that is two orders of magnitude higher than sbcl/ccl
clisp was ind the middle of things; executable image was about double that of ecl, it's startup performance is better.
1: https://github.com/jasom/image-bench https://github.com/jasom/image-bench
- mark_l_watson 11y agoThanks for the info on CCL's image size - that makes CCL worth switching to for bundling applications, but your SBCL patch sounds even better. That said, it has been a number of years since I sold a Lisp application - but still good to know!