Skip to content

Commit 855b5e7

Browse files
committed
Record why the baseline table is empty, and where the run is tracked
docs/performance-baseline.md now names the real blocker: this host cannot build the deepseek-harness checkout (no git for its version step, no C compiler for the native/system addon), so dev/bench.sh cannot boot a bench. The attempt is tracked in #2571 and the four rows stay unmeasured rather than invented. Fixes #356
1 parent c55205c commit 855b5e7

1 file changed

Lines changed: 1 addition & 4 deletions

File tree

‎docs/performance-baseline.md‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,10 +66,7 @@ Scenario rows are `turn end-to-end` (ms), `tool-call latency` (ms), `resident RS
6666

6767
## First baseline on the maintenance box
6868

69-
**Not measured yet.** The delivery workflow that wrote this page runs on a host with neither a
70-
`deepseek-harness` checkout nor `pnpm`, so `core/dev/bench.sh` cannot boot a bench there and the
71-
four rows would be invented rather than measured. Recording invented numbers would be worse than
72-
an empty table: the point of this page is that a later run can be compared with it.
69+
**Not measured — this host cannot build the deepseek-harness checkout (no `git`, no C compiler); tracked in #2571.** The checkout present here is pristine source, and building it needs `git` for its version step and a C compiler for the `native/system` addon, so `core/dev/bench.sh` cannot boot a bench and the four rows would be invented rather than measured. Recording invented numbers would be worse than an empty table: the point of this page is that a later run can be compared with it.
7370

7471
The command above is the run to do, and the commit to record is the one that added
7572
`core/dev/perf-baseline.mjs`. The table to fill is:

0 commit comments

Comments
 (0)