Repository navigation
Performance: benchmark cold and cached extraction - #96
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #46
What changed
zig-out/benchmark/results.json, enforce evidence-backed regression budgets, and preserve artifacts even when a budget failsHosted evidence
f0559163589aa672d1e8f68265967864ffcdf2f52665af936efe6cd2947193b5budgets_enforced: true; total, per-stage, per-cached-iteration, and memory budgets all passedLocal QA
zig fmt --check build.zig build.zig.zon src benchmarkpython -B -m unittest scripts.test_install_zig(5 tests)python -B scripts/check_ci.py(10 immutable actions, 6 Zig archives)zig test benchmark/contracts.zig(3 tests)zig build benchmark-check(5.21 s total, 5,966,099 peak tracked bytes, zero final tracked bytes)zig build test(complete 529-test suite)