I work on Dolt, the first SQL database with git-like version control, written entirely in Go. And as a rule, databases need to be fast. So we have lots of tests in our CI workflow to monitor performance regressions before they ever hit our main branch. Last month, a commit that was supposed to be a no-op refactor caused a 30% regression in sysbench's types_scan benchmark. Pictured: An example of what you don't want to see on your GitHub PR. Uncovering the root cause of this regression turned out...