Keynote: New Heights
summary
Phoenix reaches two million channel clients on one server using 45 Rackspace load generators and a 40‑core 128 GB box that uses about 83 GB RAM, successfully broadcasting a Wikipedia article to 2M sockets in ~2 seconds. Optimizations include fixing a central timer bottleneck, switching ETS table type for O(1) inserts, and sharding PubSub to parallelize broadcasts. Presence implements a ORSWOT CRDT with heartbeat/vector clocks for eventual consistency and shows node down/up recovery working in real demos.
AI-written summary · about
chapters (39)
- 0:00Intro
- 0:25New Heights
- 0:57Phoenix
- 1:19Milestone
- 1:51Benchmarking
- 3:00Memory Usage
- 3:10Connection Limits
- 3:50Phoenix Core
- 4:10Wikipedia
- 5:34Chat Room
- 6:51Optimisation Story
- 10:15Performance Story
- 12:24Memory Leak
- 12:42GitHub Issue
- 13:22Phoenix Core Bug
- 13:45One Line of Code Change
- 14:55The Problem
- 17:10Process ID
- 17:25Binary Representation
- 18:49PubSub
- 19:36Presence
- 23:14Best case scenario
- 23:34No 2 is gone
- 24:21Problems
- 24:45CS Research
- 25:14CRTT
- 26:32Heartbeat Protocol
- 27:53Vector Clocks
- 30:01Node 3 Heads
- 30:32Server API
- 32:27Fetch Callback
- 33:25JavaScript
- 34:38Demo
- 38:33Echo
- 39:45Minitomini associations
- 39:57Concurrent transactional tests
- 40:40Service discovery
- 43:44Optimizations
- 46:52Community
related talks
58mKeynote – Chris McCord
40mThe Road to 2 Million Websocket Connections in Phoenix
18mKeynote: Mind the Gap: Bridging Cloud Native Innovation with Real-World Use
01h 03mKeynote: Off the Rails
18mHigh-Load Systems: Challenges in Social Network Development
30mAbove the Clouds: Investigating Systems from 32,000 ft.
43mRealtime performance at scale (...)
45mKeynote Address: Netflix: Streaming Entertainment to 200 Million Members Around the World