diff --git a/.github/runs-on.yml b/.github/runs-on.yml index 4c6903d1..95eea8ae 100644 --- a/.github/runs-on.yml +++ b/.github/runs-on.yml @@ -6,10 +6,8 @@ runners: # Used by .github/workflows/bench_bare_metal.yml. # - # Every field is pinned rather than ranged. Bencher compares each run against - # this testbed's own history, so a different instance type or core count is a - # step change in the series rather than a data point -- widening any of these - # means retiring the testbed and starting a new one. + # Pinned rather than ranged: the testbed is named after this CPU and its core count, so widening + # any field renames the testbed and stops the old series rather than corrupting it. bench: # Avoid expand to partial family family: ["c7i.4xlarge"] diff --git a/.github/workflows/bench.yml b/.github/workflows/bench.yml index ee7d701f..3aa71c4a 100644 --- a/.github/workflows/bench.yml +++ b/.github/workflows/bench.yml @@ -1,8 +1,6 @@ name: Benchmark -# Shared body of the Bencher continuous-benchmarking runs. Callers choose the -# machine and the Bencher testbed; everything downstream is identical, so the -# testbeds stay comparable in shape even though their absolute numbers are not. +# Shared body of the Bencher runs; the caller names the machine and the benches/LADDER.md rungs. on: workflow_call: @@ -11,24 +9,17 @@ on: description: Value for the job's `runs-on`. required: true type: string - testbed: - description: Bencher testbed. Must change whenever the hardware does. - required: true - type: string label: - description: Benchmark label, used to name the result artifacts. + description: Result-artifact prefix; each rung uploads as `