Overcoming migration hurdles
summary
Migrating general compute to AWS Graviton cuts costs and raises throughput by switching compiled artifacts and CI builds to Arm instances; CircleCI supports this with a Graviton-managed build fleet, runners in VPCs, cross‑architecture pipelines and just one configuration change to resource class. Honeycomb validates the approach by running parallel x86/Arm jobs via parallel CI builds and feature‑flagged rollouts, spotting a 10% median latency win, dramatic Lambda cost drops, and customer examples of 50% faster builds and 50% lower costs at scale.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:47The problem: Software teams want to move faster but can struggle to do so
- 8:48AWS: Broad choice of processors
- 9:15AWS Graviton processors
- 10:04Why AWS Graviton?
- 12:15Start with the right foundation
- 13:15Complete the steps to migrate
- 14:57AWS Graviton and CircleCl Arm compute collaboration
- 16:20Standard Linux config Arm config
- 21:57Honeycomb's challenge
- 23:46Gaining confidence in production
- 26:43New ingest path case
- 28:14AWS Lambda on AWS Graviton lowers TCO
- 30:44Cost savings
related talks
31mContinuous Delivery on Arm: A Practical Approach
01h 14mModernizing and Optimizing Applications for the Cloud
34mARM Migration Made Practical
36mWhy and How to Choose Arm64 for your Cloud Applications
19mHigh availability with CloudBees CI on AWS Graviton3 and Amazon EKS
34mScheduling in CI/CD systems
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline
40m"Cloud Cost Optimization for Java Developers"