BEAM: What Makes Erlang BEAM
summary
BEAM explains how Erlang gets scalability and uptime by specific mechanisms: lightweight processes with isolated heaps and a scheduler per core, message sends that copy into the recipient heap (process mailbox copy on send), per-process garbage collection, hot code upgrade and supervisors for fault containment, compact I/O using iolists as trees, binary parsing via the bit syntax, and real incidents like a process growing past 32 GB, a 4096 try_captures static limit and term_to_binary counted as one reduction causing a watchdog kill.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 4:25Problem with growth
- 5:08Problems
- 11:53History
- 13:31Plex
- 14:46Airline
- 15:31Language and Thinking
- 17:20Exception Handling
- 17:59Be Explicit
- 22:02BEAM
- 25:01Memory Handling
- 26:07Interactive Shells
- 27:50Strings
- 30:11Bit syntax
related talks
52mErjang - With the JVM under the Hood
01h 06mWhat every Node.js developer needs to know about Elixir
52mRobotics and Sensors Using Erlang
16mHarnessing the power of the Erlang VM
38mCloud Scale Erlang
40mHTTP/2 in Erlang
28mEvented Ruby vs Node.js
05mLightning Talk: C++ in the Cloud: One NIF at a Time with Elixir