Răsfoiți Sursa

AGENTS: bench flag semantics (optional label, opt-in depth)

Alexander Korolev 1 săptămână în urmă
părinte
comite
9ef54874b6
1 a modificat fișierele cu 6 adăugiri și 3 ștergeri
  1. 6 3
      AGENTS.md

+ 6 - 3
AGENTS.md

@@ -91,10 +91,13 @@ keeps the green (the fix for a confirmed stale row is `runlock close`).
 `<UTC-date>_<label>.{md,json,log}` in `recipes/<lane>/reports/` — it does the
 scratch-cwd/absolute-json/log juggling, polls the API for readiness first,
 and prints the final score + perf rows. Defaults: seed 42, hardmode, perf,
-concurrency 1,2; served name/port from the recipe.
+concurrency 1,2; served name/port from the recipe. `--label` names the
+campaign record — required for quality runs, optional for `--perf-only`
+(defaults to `perf`). The depth suite (`--depth`, 16K..256K) is opt-in —
+a full sweep takes ~45 min on a 2x lane.
 
-**Depth suite:** every campaign also appends a perf-only depth sweep
-(`src/bench_depth.rs`): depths `16384,65536,131072,262144` at **c1 and c2**,
+**Depth suite:** every campaign appends a perf-only depth sweep
+(`src/bench_depth.rs`, `--depth`): depths `16384,65536,131072,262144` at **c1 and c2**,
 2 runs per point, pp2048/tg128, same log file → the report's Throughput
 table gets the long-context rows; a depth failure only warns. Both perf
 paths pass `--benchy-args=--enable-prefix-caching` — **without that flag