Brummel/AILang
1
0
Fork 0
Code Issues 29 Pull Requests Actions Packages Projects Releases Wiki Activity

*.bump_s throughput baseline is stale vs current hardware #15

New Issue
Closed
opened 2026-05-20 13:21:58 +02:00 by Brummel · 0 comments
Brummel commented 2026-05-20 13:21:58 +02:00
Owner
Copy Link
Copy Source

bench/check.py's throughput.*.bump_s family (the fastest, most jitter-prone metrics) reads ~+5–13% over bench/baseline.json on the current machine. Localised at the iteration-discipline-revert audit (2026-05-16): an interleaved 3×60-run measurement of bench_list_sum bump_s built from the byte-oracle commit 1ff7e81 shows the same ~+11% elevation as HEAD, and the two bump binaries are cmp-identical — so this is environmental drift relative to the 2026-05-09 baseline-capture machine state, not a codegen regression. Re-capture the full *.bump_s set on current hardware from a known-clean commit and recalibrate the bump_s baseline+tolerance pair (or widen the tolerance) so the noise floor stops tripping check.py exit 1. Pure bench-harness recalibration; no language change.

`bench/check.py`'s `throughput.*.bump_s` family (the fastest, most jitter-prone metrics) reads ~+5–13% over `bench/baseline.json` on the current machine. Localised at the iteration-discipline-revert audit (2026-05-16): an interleaved 3×60-run measurement of `bench_list_sum` bump_s built from the byte-oracle commit `1ff7e81` shows the *same* ~+11% elevation as HEAD, and the two bump binaries are `cmp`-identical — so this is environmental drift relative to the 2026-05-09 baseline-capture machine state, **not** a codegen regression. Re-capture the full `*.bump_s` set on current hardware from a known-clean commit and recalibrate the `bump_s` baseline+tolerance pair (or widen the tolerance) so the noise floor stops tripping `check.py` exit 1. Pure bench-harness recalibration; no language change.
Brummel added the bug label 2026-05-20 15:29:34 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Core functionality broken — takes precedence over everything else in the queue. /boss preempts current work to handle it
 bug
Observable misbehaviour — surface inconsistency, false positive, wrong output
 feature
Smaller addition inside a milestone, no full spec
 idea
Not yet decision-ready, no commitment
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/AILang#15
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?