Synchronizing Game Components
summary
Argues that scaling games needs isolated processes and message-passing rather than shared mutable state, implements it in Erlang with a small L-like language, and demos a 500×500 universe running 1,000 ships (run/timid/attack/flock behaviors) talking to a central universe and display process. Shows load moving across 8 cores, proves pure message-copy only communication scales and that blocking synchronous requests rapidly stall the system.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:25Game Implementation
- 4:20Classical Implementation
- 17:45Go Fully Parallel
- 21:02Example
- 23:14System Overview
- 24:45Demonstration
- 31:19timid ships
- 35:55demo
- 37:31synchronous communication
related talks
49mThinking in a Highly Concurrent, Mostly-functional Language
25mErlang-based Desynchronised Urban Traffic Simulation (...)
40mDistributed, Eventually Consistent Computations
38mThree Games In Elixir
43mFine-grained everything
42mGame of Threads - You Spawn or You Die
43mClosing Keynote
05mGameDev in Elixir using ECS and Live View