CPU simulated benchmarking for GKE cluster. #143
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
MattIrv
approved these changes
Oct 7, 2024
jdnurme
approved these changes
Oct 7, 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.
Simulated CPU benchmarking code for GKE cluster. I have tested this on GKE cluster of 20 N2-standard-64.
Example of deployment-yaml: http://gpaste/6024689370791936
Using linear model here since it is easier to divide it amongst the processes (in order to ensure consistent size across the processes) .
Also not using trainer object (& trainer.fit) since training does consume some time (decreases dev velocity) and also produces checkpoints of varying sizes.
I will have a separate version of similar code which can be run on cloudtop for quick testing.