Keynote: Erlang Powered Rabbits
summary
Explains why RabbitMQ leverages the Erlang VM: RabbitMQ maps one Erlang process per connection, channel and queue and benefits from 1 ms time slice scheduling that keeps low-priority queues responsive while hot queues are throttled. Benchmarks show ~100k–150k msg/s spikes, ~40k on one core and ~1M msgs/s on 48 cores; JIT yields about 20% performance boost. Per-process garbage collection can temporarily double a process’s memory during collection; distributed nodes scale to hundreds but hit network and sequential bottlenecks.
AI-written summary · about
chapters (9)
- 0:00A bit of History
- 11:20Erlang in Rabbits
- 12:55Fairness
- 21:41Erlang in RabbitMQ
- 24:15Parallelism
- 26:28Process Characteristics
- 27:12Distributed Computing
- 28:40What about Erlang the Language?
- 32:4843:56- QnA
related talks
36mDRb vs. RabbitMQ Showdown
54mKeynote: Bringing a Ferrari to a Horse Race
26mBreaking Magical Barriers
51mThe Erlang VM or How I Started Loving Parallel Progamming
59mDissecting the Rabbit RabbitMQ internal architecture
59mDissecting the Rabbit RabbitMQ internal architecture
01h 01mThe Erlang Ecosystem
42mThe Soul of Erlang and Elixir