bench

Overview ¶

Command bench runs HTTP latency scenarios against a target shithub instance and emits one JSON record per scenario to stdout. The output is structured for ingestion into a perf-baseline file.

Usage:

go run ./bench -target=http://localhost:8080 -iters=20 > out.json

`make bench-small` invokes this against the dev instance with a short scenario list; `make bench-full` is the placeholder hook for the nightly run that exercises big-fixture scenarios (1M-commit repo, 100k-issue repo) — those fixtures aren't generated by this harness yet (the seed cost is non-trivial; see fixtures/README.md for the planned generators).

The "harness in the repo, not external" choice is per the S36 design notes: keeps perf-as-a-feature visible in PR review.