What to know before adopting Arm: Lessons learned at Datadog
summary
Datadog moves tens of thousands of hosts to AWS Graviton and reports a 25,000% rise in Arm64 hosts since Graviton2, but migration uncovers concrete surprises: Envoy 1.16→1.20 shows about 50% higher CPU per request on early Arm builds, QEMU emulation triples or worse image build time (hello world 23s→64s, toolbox 16m→90m), so teams deploy Arm64 builders, fix OverlayFS/user xattr issues for rootless builds, and a tag-normalization tweak cuts intake CPU by 5% (hundreds of thousands USD saved).
AI-written summary · about
chapters (13)
- 0:00Introduction to Graviton
- 2:43About Datadog
- 4:41Early ARM Adoption
- 7:21Analyzing Migration Trends
- 10:26Technical Environment
- 11:57Migration Strategy
- 15:36Execution and Iteration
- 18:45Performance Challenges
- 24:07CI/CD and Emulation
- 28:13Docker Build Issues
- 34:25Software Maintenance
- 35:32Optimizing Application Code
- 40:33Summary and Conclusion
related talks
36mWhy and How to Choose Arm64 for your Cloud Applications
34mARM Migration Made Practical
31mOptimizing Cost and Performance with arm64
27mWhat's Going ARM: Adopting ARM64 At Airbnb
01h 14mModernizing and Optimizing Applications for the Cloud
06mChange Your Architecture and Save the World
52mUbuntu on ARM
22mGraviton