What is Performance Driven Development and why aren't you doing it?
summary
Asserts performance failures live in code not caches, demonstrating a legacy CRM wired through Solr and custom Redis layers that ships 286 queries and takes 11.92s to load then is refactored to 4 queries and 324ms. Recommends profiling and CI gating with Blackfire or Tideways, local inspection with Xdebug / kcachegrind or Laravel/Symfony debug bars, and embracing async webhooks (Vonage Verify example) plus ORM query awareness and junior training.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:32Performance Driven Development
- 10:35Real-world performance issues
- 13:46Why performance matters
- 16:57Enterprise performance mistakes
- 19:05Performance optimization tooling
- 20:50Performance mindset
- 23:36Manual performance debugging
- 27:04Framework debug tools
- 28:29Adopt Performance Driven Development
- 32:21Defining Performance Driven Development
- 33:24Why aren't developers doing Performance Driven Development
- 35:11Q&A
related talks
41mPerformance Engineering in the Age of DevOps and Agile
48mBuilding Really Fast Applications
29mProgressive Testing to Meet the Performance Imperative
42mAdding Performance Assertion to Standard Functional Testing
01h 00mPerformance In Modern Times: An Evolutionary Journey
28mPerformance is a Feature It Should Be Tested as Such
25mGetting your Team Passionate About Web Performance to Achieve Performant Web Apps
56mBetting on Performance: A note on Hypothesis-driven Performance Testing