Live data from Hacker News

AWS EC2 Spot instances can now be stopped and started like On-Demand instances

aws.amazon.com

1–10 of 17 posts

Re: AWS EC2 Spot instances can now be stopped and started like On-Demand instances

#8
Spot also supports hibernate on some instance types: https://aws.amazon.com/about-aws/whats-new/2017/11/amazon-ec...

Hibernate is just like good old hibernate from windows XP days. You save the RAM to disk. And resume your processes on next boot and they won't even notice they were stopped! (Except for the time has changed...)

It might be really helpful for low priority batch processing.

Disclaimer: I've never tested this.

Re: AWS EC2 Spot instances can now be stopped and started like On-Demand instances

#9

Spot also supports hibernate on some instance types: https://aws.amazon.com/about-aws/whats-new/2017/11/amazon-ec... Hibernate is just like good old hibernate from windows XP days. You save the RAM to disk. And resume your processes on next boot and they won't even notice they were stopped! (Except for the time has changed...) It might be really helpful for low priority batch processing. Disclaimer: I've never tested…

Neat! Did not know that. Thanks :-) The 100GB RAM cap seems rather limiting though.

The ideal case scenario imho (one step beyond this stop/start-at-will feature) would be "convertible" spot - being able to migrate to on-demand with zero downtime when ec2 needs that capacity back - that'd solve a lot of my problems.

Re: AWS EC2 Spot instances can now be stopped and started like On-Demand instances

#10

Spot also supports hibernate on some instance types: https://aws.amazon.com/about-aws/whats-new/2017/11/amazon-ec... Hibernate is just like good old hibernate from windows XP days. You save the RAM to disk. And resume your processes on next boot and they won't even notice they were stopped! (Except for the time has changed...) It might be really helpful for low priority batch processing. Disclaimer: I've never tested…

Neat! Did not know that. Thanks :-) The 100GB RAM cap seems rather limiting though. The ideal case scenario imho (one step beyond this stop/start-at-will feature) would be "convertible" spot - being able to migrate to on-demand with zero downtime when ec2 needs that capacity back - that'd solve a lot of my problems.

You can (effectively) do that already -- just set your spot bid to the maximum you're willing to pay, i.e. the on-demand price.
Post reply on HN