Performance Engineering in the Age of DevOps and Agile
summary
Argues performance becomes a continuous feature: add a JIRA checkbox on every story so teams evaluate impact, run baselines in CI/CD for response times and DB/service call counts, and create observability dashboards before code deploys. Builds include mocked third parties for scale tests and a production-safe harness that runs weekly Cyber Monday load tests to catch issues no lab finds. Finds concrete bugs — a developer’s three-second wait vs timeout — and uses APMs and synthetic traffic to verify fixes and enforce P95 budgets.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:27About Gopal
- 2:01Traditional performance engineering approach
- 2:32Technical challenges
- 3:41Fundamental mental approach
- 5:14Responsibility for performance
- 5:34Thinking about performance
- 5:48Performance is impactful
- 7:45Service Level Agreements
- 10:03Performance in Agile
- 12:20Testability
- 14:12observability
- 15:36testing
- 17:36Lab
- 19:24Production
- 21:45Monitoring
- 23:24Prior Prior Responsibilities
- 23:55Winning Hearts and Minds
- 24:34Keeping Score
- 25:38Work with Teams
- 26:27White Papers
- 26:59Conclusion
- 38:05Demonstrating Value
- 39:40When should you optimize
related talks
33mPerformance Testing in Agile and DevOps
41mContinuous Performance Testing in DevOps
01h 00mPerformance In Modern Times: An Evolutionary Journey
44mContinuous Performance Testing in DevOps
29mProgressive Testing to Meet the Performance Imperative
31mEvolving performance assurance
12mPerformance Engineering: We the people have spoken
40mWhy component level performance testing should always be part of CD and CI