Bench log: the fairness re-check of the variant race (jobs 0.17 to 2.8 s during a race, 36 s before)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-04 21:12:40 +00:00
parent 08f810009b
commit b83d9e1f5b

View file

@ -1116,8 +1116,11 @@ race on A `winner g256 14.207 base 11.404 gain +24.58%` (compile 563 ms, 36 s of
35,554 ms = program 58 ms, dataset 524 ms, race 34,972 ms (`winner mt512-g256 12.807 base 10.346 gain +23.79%`),
the swap to B in 0.01 ms, the 64-nonce job across the 32-bit boundary 14.8 ms. Found by this check: the job queued
during a race waited for the whole race (job 2 done after 35,946 ms; the mutex is not fair), so the race now
pauses 150 ms after every window (commit 32d1c01); the re-check of that pause is queued under the `run` lock
behind a 3-hour network run and is reported in the agent's hand-over if it ran.
pauses 150 ms after every window (commit 32d1c01). Re-check with the pause (`--serve`, a job every 3 s through
both races, load average 134 to 183): every job during the deferred race on A and the prepare race on B finished
in 0.17 to 2.8 s (33 jobs, none over 2,831 ms, versus 35,946 ms before), the race on B 39.8 s inside a
40.2 s prepare, winner g256 both times, swap 0.01 ms, 0 errors; the race's own windows were 2 to 3 s longer
in total than without the pause, as expected.
NVIDIA side, what the Mac could check: `proto-cuda/nvrtc/emu/test.sh` PASS on the race build (the race off under
emulation, "variants 1 base only, no race (emulation)" logged per pair; 9 source checks PASS, the --serve protocol