Add structured compiler diagnostics
This commit is contained in:
parent
0fe968c475
commit
24bd13f9d9
20 changed files with 1386 additions and 58 deletions
|
|
@ -15,6 +15,18 @@ Run the 1,000-node generic baseline:
|
|||
make benchmark
|
||||
```
|
||||
|
||||
Run the Milestone 1 warm-operation counter and latency smoke gate:
|
||||
|
||||
```bash
|
||||
make benchmark-m1-smoke
|
||||
```
|
||||
|
||||
Run the maintained 1,000-node Milestone 1 benchmark:
|
||||
|
||||
```bash
|
||||
make benchmark-m1
|
||||
```
|
||||
|
||||
The benchmark creates canonical sources, derived state, changesets, rendered output, and caches
|
||||
only in a disposable temporary directory. It does not read another project, self-host DocForge, or
|
||||
mutate repository content.
|
||||
|
|
@ -27,3 +39,9 @@ must explain fixture or environment changes before comparing results.
|
|||
The generic fixture exposes whole-source scaling. It does not replace the incremental adapter
|
||||
equivalence tests and does not claim to measure a portable graph renderer, because Milestone 0 has
|
||||
no portable graph-planning or graph-rendering contract.
|
||||
|
||||
The Milestone 1 harness treats wall time and structured work counters as separate gates. Warm
|
||||
operations fail if they load a complete project, parse source files, reconstruct an adapter
|
||||
projection, extract adapter sources, build an index, prepare a render, construct rendered output,
|
||||
or hash complete rendered output. Its latency ceilings are the Milestone 1 targets, not claims
|
||||
about all hardware.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue