Re:"time to GPT-2", down to 2.91 hours
by janalsncm on Wednesday February 04, 2026 @05:39AM
(#46884121)
Never used gpu spot instances before but I would have to imagine getting interrupted is pretty annoying.
[ Parent
| on HN ]
Re:"time to GPT-2", down to 2.91 hours
by somehowadev on Wednesday February 04, 2026 @06:31AM
(#46884556)
As long as your workload can handle resuming again and your instances aren't heavily in-demand (looking at the eviction rates), the cost saving for us is substantial enough to take the occasional interruption.
I do wish Azure gave more than the 30 second eviction warning (like AWS) but still useable.
it depends, our workloads can finish up in under two minutes and shut down without much effort, so we haven’t really noticed it outside of one time when we had no spot capacity.
Re:"time to GPT-2", down to 2.91 hours
by janalsncm on Wednesday February 04, 2026 @05:58AM
(#46884287)
I guess if checkpointing is set up correctly and your runtime is saved to a docker image it’s feasible. Probably not going to get a 3 hour continuous chunk of time I would assume.
Re:"time to GPT-2", down to 2.91 hours
by direwolf20 on Wednesday February 04, 2026 @06:58AM
(#46884801)
When I once used Spot it wasn't that bad. You're likely to have an instance for 3 hours.
I use spot for my gmod server. Contention is higher for GPU, but I only saw disruptions maybe once every 2 months for super common instance types. We scale up and down more frequently than we get disrupted.
In addition to the two-minute interruption notice, rebalance recommendations[0] allow you to handle interruptions even more gracefully.
[0] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/rebalanc...