Lightning Talk: Performance Metrics Driven CI/CD in a Nutshell
summary
Argues for shifting performance left into CI/CD by adding concrete metrics to pipelines: track a response time corridor, count SQL calls to catch the n plus one anti-pattern in microservices, monitor exception rates and tier-skipping calls, and measure front-end(page) metrics like domain count, image count and size. Cites business impact — Amazon sees ~100 ms affecting revenue by ~1%, Walmart ~1000 ms by ~2% — and recommends failing builds on regressions.
AI-written summary · about
chapters (5)
- 0:00Introduction to devops
- 0:52Pipeline automation
- 2:08Performance in production
- 3:33Key performance metrics
- 5:20Closing and resources
related talks
37mBuilding a Metrics Optimised Pipeline (Full Automation)
40mWhy component level performance testing should always be part of CD and CI
41mPerformance Engineering in the Age of DevOps and Agile
13mLightning Talk - CI/CD Patterns
33mMeasuring Developer Efficiency in DevOps: Key Questions, Metrics, Best Practices
33mPerformance Testing in Agile and DevOps
13mLightning Talk: Observability-First DevSecOps: Building Resilient Multi-Cloud P...
33mHigh performing engineering teams and the Holy Grail