My CI perf budget failed twice on changes that couldn't be slower

<p>The perf job failed on a change that couldn't have made anything slower. I reran it and it passed. It happened again on the next one.</p> <p>That is the moment a performance budget stops being useful: nobody trusts a red build that goes green when you click "re-run". I could have loosened the budget. Instead I kept it and made each number say whether the app or the machine was slow. This is how

Read the source →