The change that gave me my biggest win of the event was scored 1.004x, "no clear difference" by my own A/B rig, with a 95% confidence interval of 0.978 to 1.019. On the real box it cut my parse phase from 28.5 ms to 19.9 ms.
This post is about that gap. I spent Speed Demon 2026 (a Hackathon Raptors performance hackathon) making two Rust programs about 1,200x and 360x faster than their Python references. But the thing I actually learned was not a trick for making code fast. It was that every instrument I used to decide "keep or revert" was blind to something specific, and I didn't find out which blind spot was which until I tested the instruments themselves.
Repo: https://github.com/FrankChinedu/speed-demon (team Deez-attacher; I did tracks A and C, a teammate did B and D).
The setup, briefly
Track A (ingest): aggregate 3.1M log lines into per-endpoint counts, p50/p95/p99 latency and error rates per hour.…