Commit e2f9d3f
Widen kernel launch latency tolerance to cover scheduler variance
The latency benchmarks measure identical launch code at values that differ by
a uniform ~3.5 microseconds depending on which GPU and CPU cgroups SLURM
assigns to the job: builds 7080 and 7081 ran the same host launch path on the
same node and measured 16990 vs 20530 ns (GPU index 3 with CPU 3 vs GPU index
0 with CPU 0). An atol of 2000 ns cannot distinguish this assignment variance
from a real regression, so raise it to 4000 ns, shared by all three
benchmarks. A genuine per-launch regression like the one caught in round 17
(+7000 ns) would still fail.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>1 parent 45db370 commit e2f9d3f
1 file changed
Lines changed: 8 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
34 | | - | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
35 | 40 | | |
36 | 41 | | |
37 | 42 | | |
| |||
45 | 50 | | |
46 | 51 | | |
47 | 52 | | |
48 | | - | |
| 53 | + | |
49 | 54 | | |
50 | 55 | | |
51 | 56 | | |
| |||
58 | 63 | | |
59 | 64 | | |
60 | 65 | | |
61 | | - | |
| 66 | + | |
62 | 67 | | |
63 | 68 | | |
64 | 69 | | |
| |||
0 commit comments