Instant-Launch Erlang Executables
summary
Single-file Erlang executables pack a pre-captured runtime state so startup skips most loader work, using a rebar plugin to record and pre-transform beam binaries and an mmap-backed image to replay that state. Benchmarks show warm startups drop from ~41 ms to ~18–20 ms (about 2–3×), Elixir boots from ~75 ms to ~20 ms, and rebar from ~125 ms to ~70 ms. Prototype tooling (Kaizen/Calzone plus launcher) runs as one binary and demonstrably works on Linux.
AI-written summary · about
chapters (12)
- 0:00Instant-launch Erlang executables
- 2:25Elixir binaries limitations
- 3:34Kaizen project for Erlang
- 7:45Pre-loading binaries for speed
- 9:49mmap accelerates startup
- 12:36Integration with rebar3
- 13:17Live demo launcher
- 15:21Benchmarking startup gains
- 18:38Rebar3 and Elixir speed
- 20:21GRiSP Nano hardware
- 22:25Future plans and community
- 24:10Q&A
related talks
48mElixir by the Bellyful
40mUnderstanding Erlang Kernel
19mElixir – what it is and why is it amazing?
42mIt's about (run)time -- Elixir beyond the hype
42mThe Soul of Erlang and Elixir
42mIntroduction to Elixir for Rubyists
54mKeynote: Adoption
45mElixir: une potion pour mixer complexité et concurrence en temps réel