Update Runtime Bugets and Step Hints - #838
Merged
priyakasimbeg merged 7 commits intoFeb 10, 2025
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
Sorry, something went wrong.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Depends on #830, #831, #832, and #833.
This PR updates the runtime budgets and step hints according to our working group discussion and issue #836.
For runtimes and step hints, I have always rounded up to the nearest integer.
The new budgets are:
External tuning
Self-tuning
Change the factor from 3x to 1.5x. This keeps the baseline and Schedule-free AdamW still within finite workload scores (except ResNet, which could not be achieved, even with the 3x budget).