#341 Reduce Databricks runs#344
Merged
Merged
Conversation
Drop broadcast-12-nodes-large and partitioned-12-nodes-large from
benchmarks.yml, their entrypoint files, dispatch arms, docker-compose
services, and CI matrix rows. Fold the orphaned 4-node-large entries
into the existing {2, 16}-node batches (3-way, vCPU sum = 100).
Introduce BENCHMARK_MAX_FIXED_WINDOW_SECONDS (4500s) and check it in the use_sequential_stopping=False branch of @monitor so a pathological iteration cannot convert directly into unbounded billed node-hours.
Closed
6 tasks
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.
Summary
BENCHMARK_MAX_FIXED_WINDOW_SECONDS) for fixed-iteration benchmarks to cap worst-case costCloses #341
Test plan
python -m compileall src main.py benchmark_runner.pypassesrelated_script_idsresolve bidirectionally