Find the Performance Regression
Narrow a performance regression using golden signals and binary search over changes.
Performance regression Search p95 moved from 380 ms to 1.9 seconds after a release with 47 commits. Errors are flat. Users feel the delay. The team needs a narrowing strategy, not a debate about whose commit looks expensive. Signals plus bisection Define the slow behavior, then split the change set Golden signals describe the regression. Bisecting tests the history until one change explains it. Shortcut Profile the whole service and argue from flame graphs. The team finds an N+1 lookup instead of reverting a whole release. A benchmarked midpoint is stronger than a hunch about expensive code. 01 Signals 02…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in