Rewrite Pion in Elixir
summary
Reimplements Pion pieces in Elixir and ships STUN TURN ICE implemented plus RTP/RTCP parsers and a work‑in‑progress DTLS peer connection, comparing against Pion (Go) and coTURN (C). Benchmarks on 32‑core machines show Elixir TURN is ~2.5× slower than coTURN in small datagram tests, ~2× slower at a 5 Gbps video scenario (45% vs 15% CPU), but scales to 2–4k connections at 5 Gbps after switching to RuPort multiple listeners and per‑thread sockets. Code and benchmarks are public.
AI-written summary · about
chapters (6)
- 0:00Introduction to WebRTC
- 1:29The case for Elixir WebRTC
- 4:28Membrane RTC engine
- 7:20Real turn server performance
- 13:43ICE and STUN implementation
- 17:58Q&A session
related talks
25mElixir WebRTC - batteries included WebRTC implementation for Elixir ecosystem
36mKnee Deep Into P2P
28mPipelining WebRTC videoconferences in Elixir with Membrane Framework
42mIntroduction to Elixir for Rubyists
32mElixir, Phoenix, and WebRTC - An Enterprise Class Soft Phone in the Browser
40mBuilding blocks and How to Use Them: A MongooseIM Case Study
44mThe NeverEnding Application
27mDistributed Robots with Elixir