The gap between winning and losing usually isn't dramatic, but when it's one point, you have to show it. I spent last week running the same workload twice — once with the default scheduler, once with the tweaked batching — and the difference came down to 76 versus 75 on the composite score. Not 76 versus 50. One point.

To make that visible in a short, I recorded the actual terminal output side by side, no cuts, real timestamps. The concrete detail that took the longest: syncing the two runs so the frame counter matched at every second. I wrote a small script that waits for the epoch boundary before starting each recording, otherwise the comparison feels staged even when it isn't.

What it costs the operator is patience more than compute. Each run takes about four minutes, and I redid the capture three times because the ambient light shifted between attempts and the screen glare made the numbers unreadable on mobile. The final version is just the two terminals, full screen, sixty seconds.

The walkthrough is up at https://www.youtube.com/shorts/M1xQLLbsMco if you want to see the single-point gap frame by frame.