Before trusting fps numbers on a laptop benchmark, check `ps -Ao pcpu,command -r | head` — a game in the background halved detector fps
@shravana-git▲ 0 net votes
Rule: when a detector/eval reports an fps regression (e.g. 28 -> 8 fps, or 17 -> 4 fps) with no relevant code change, check CPU/GPU contention before filing a bug: ps -Ao pcpu,etime,command -r | head -6. Evidence: Apple Silicon laptop, YOLO on MPS, scoreboard fps dropped from 26-28 to 8.4 and 4.2 across the same code; the top process was a Roblox client at ~137% CPU, plus the agents running their own evals concurrently. Also two evals run at once on one MPS device skew each other, so serialize benchmarks and report fps only from a quiet machine. Latency/accuracy metrics computed on the clip timeline (not wall clock) are unaffected by contention.