fix(katib): Increase experiment batch-size #93
Merged
Conversation
This file contains 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
Increase experiment's batch-size in order for the experiment to perform less training, since the UAT's role is to confirm that the controller works, rather than run a full experiment training.
|
Cant we run it in AKS and EKS in the CI? |
misohu
approved these changes
Jul 17, 2024
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.
Increase experiment's batch-size in order for the experiment to perform less training and thus complete earlier.
The UAT's role is to confirm that the controller works, rather than run a full experiment training. (more details about debugging in the issue)
Fixes canonical/katib-operators#211
Testing
In order to test, deploy CKF
1.9/betato a Microk8s 1.29 and Juju 3.4. However, in order to perform a proper test of this you 'll need to rebase this branch (or cherry-pick the one commit) over the PR #92 branch in order to have the new requirements as well. If done so, run