iterative / iterative/cml.dev

clarify spot instance pricing

Open
#285 1 comment 0 reactions 0 assignees View on GitHub
documentation external-request p1-important
Dominant language
TypeScript
Stars
13
Forks
22
PR merge metrics
No merged PRs in 30d

Description

1. a high enough max bidding price (confusingly named `--cloud-spot-price`) is required to get a spot instance
2. after a spot instance is running:
- [if the spot price rises above the maximum (specified above), AWS EC2 interrupts your spot instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html)
- also, AWS can (and does) often interrupt it anyway (regardless of your bidding price) unpredictably
So basically there's no way to make spot instances never interrupt. Instead you need to either use on-demand (costs $$$ more ongoing), or program some [recovery logic](https://iterativeai.slack.com/archives/C01900GSB4J/p1657801783794509?thread_ts=1657733460.262019&cid=C01900GSB4J) (costs time/dev effort one-time)
- what about other cloud providers?
- what are the conditions for resuming? what does the user need to do (#207)?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.