D86 — Reported route time covers the whole job¶
Decision¶
A route job's reported seconds covers the whole job, every portfolio variant included (variant_seconds and variants keep the per-variant times); bench/run.py with --work gives each board the cores per job (at most 8) as router threads
Alternatives¶
Keep reporting the winner's time; fewer variants or successive halving to cut the time
Reason¶
With --work all eight variants run whatever the thread count, and one thread ran them in series: the reported time was 1/5 to 1/8 of the process (doc 10 §6). More threads leave the output byte-identical (D47) and cut a board's wall time by 66–74 % at four threads; fewer variants change results