feat: Allow on demand instances for databricks job compute policy #577
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
fctczi
changed the title
fctczi
changed the title
alldoami
approved these changes
Apr 19, 2024
fctczi
deleted the
CDI-2919-update-job-compute-policy-for-preprint-linkage
branch
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
Allow the use of on-demand instances for the Job Compute policy.
Spot instances are already too flaky for ETL work. The problem is worse with GPU workloads.
GPU workloads have the additional problem of low availability and longer provisioning times.
Additional on-demand instances will be scaled down so the additional cost is only temporary when using auto-scaling.
Test Plan
Say unittests, or list out steps to verify changes.
References
(Optional) Additional links to provide more context.