10,000 Metrics at 200 Miles Per Hour: What Auto Racing Can Teach Us About DevOps
summary
Auto racing supplies concrete lessons: modern F1 cars run over 200 sensors and push telemetry through a fiber optic mesh to collect 243 terabytes in a weekend and 2 gigabytes per lap, enabling millisecond decisions via tools like McLaren Atlas. Pit crews tune human performance to hit a world record 1.91 seconds to change four tires. Logistics failures (a missing steering wheel at the Indy 500) and rebuilds (a car rebuilt in nine hours) illustrate supply chain, runbook rehearsal, chaos simulation, and measurable performance gains tied to latency.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 4:03Simplicity in engineering
- 6:57Culture and team alignment
- 11:58Observability in racing
- 15:46Performance and pit stops
- 21:48Chaos engineering
- 28:33Innovation beyond tools
- 31:18Infrastructure as code
- 34:07Enjoy the journey
related talks
13mWhat Can We Learn from Formula 1 Incident Management
34mMove Fast Build Things… Safely!
48mMove fast Build things… Safely!
36mMove fast Build things… Safely!
01h 08m0-60 in the .NET Framework - Software development for Formula 1
14mI don't think these metrics mean what you think they mean!
28mMetrics that Matter
05mDevOpsDays Boston 2023 Lightning Talks: Anton Gurov