Erlang scales robots
summary
Measures ROS on laptops and Raspberry Pis show queue size, not message size, often limits single-host latency and throughput; Python and C perform the same for small sensor messages but C outperforms for large video frames. Network tests up to 256 ROS nodes over Wi‑Fi reveal a communication scaling limit (CLV) where latency explodes and nodes collapse. Replacing only ROS’s transport with Erlang supervision runs the same face‑tracking pipeline and recovers after 50% process kills, unlike ROS which fails after ~10% kills.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:04COOPERATIVE ROBOTICS
- 2:19AUTONOMOUS DEVICES
- 4:17ROBOTICS MIDDLEWARE
- 5:25ROBOT OPERATING SYSTEM
- 6:06PURPOSE
- 7:35OVERVIEW
- 8:58REASONS
- 10:58SINGLE HOSTS: LATENCY
- 15:56CAR KIT ROBOTS
- 16:52MULTIPLE HOSTS, VERTICAL SCALABILTY
- 19:39MULTIPLE HOSTS: REPRESENTATIVE DATA
- 20:59MULTIPLE HOSTS: VERTICAL SCALABILITY
- 30:07OPENRTMAIST PROJECT
- 30:54CRITERIA OF SUCCESS
- 37:15WHAT'S NEXT
related talks
36mScaling robots -
53mScaling robots and other stuff with Erlang
44mKeynote: Erlang Powered Rabbits
40mReal Time Performance at Massive Scale
40mSo I used Erlang...is my system as scalable as they say it'd be?
35mScaling Erlang cluster to 10,000 nodes
30mBridging robotics and systems programming:Why Copper is a game changer
13mChallenges in High Performance Robotics Systems