A regression in code I didn't touch
CPU data cache associativity issues are relatively well known. Instruction cache associativity issues, less so.
While working on go code, I investigated a surprising performance regression that turned out to be caused by L1 instruction cache associativity. In the code I didn’t even change.
The investigation included usage of go toolchain, but the underlying issue is mostly language-agnostic.