Tighten BENCHMARK_GRID_CONFIG for faster asv runs#3
Merged
Conversation
Aim: cut asv run time for bench_aca_baseline. Consumption drives the inner maximization loop; assets is the next largest lever. Combined ~2–3× speedup on compile + inner solve work without changing any regime structure. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
BENCHMARK_GRID_CONFIG: consumption 10 → 5, assets 5 → 3.Why
asv aca-baseline benchmark hit the 1800s timeout on the GPU runner (compile alone was 18.6 min). Shrinking the two largest remaining continuous grids cuts inner-loop work without touching any regime.
Test plan
pytest aca-model/tests/test_benchmark.py -m long_running -x -qpasses (end-to-end simulate still runs).🤖 Generated with Claude Code