My laptop said the program peaked at 71 MB. The scoring machine said 175 MiB.
Same binary. Same data. Same Docker image. Neither number was wrong.
That was the first of many times during Speed Demon 2026 , the 72-hour performance championship run by Hackathon Raptors , when a measurement I trusted turned out to be correct and useless at the same time. Over 106 logged steps I found that almost every mistake I made had the same shape: I read a true number that was answering a different question than the one I was asking. The profiler answered "where did the samples land", not "what would disappear if I removed this". The instruction counter answered "how much work", not "what is the core waiting for". My laptop answered "how fast is this on my laptop".
This post is the list of those questions, what each wrong reading cost me, and the measurement that finally answered the right one.
The task, and a machine you never touch
I'll stay on one of the four tracks, Track B.…