17

I am considering moving from a VPS to EC2. EC2 is elastic and so is its pricing; I could boot my instance on demand, then let it shut down if it isn't active by the end of some hourly period.

How much time does that process take? Assume a micro instance booting from EBS. Assume Linux (probably Ubuntu); the 10 minute times mentioned for Windows leave me unimpressed. The transition could be ec2-run-instance (with its pending state) or ec2-start-instance. Feel free to mention the start up times of other clouds if you know them.

Community
  • 1
Tobu
  • 4,367
  • 1
  • 23
  • 31
  • Here's a pingback from the high scability blog: http://highscalability.com/blog/2011/3/17/are-long-vm-instance-spin-up-times-in-the-cloud-costing-you.html – Tobu Mar 25 '11 at 23:33

4 Answers4

9

On amazon, booting a machine off of EBS should be significantly faster than a read-only, S3 based instance - From http://aws.amazon.com/ebs/:
"You can also stop and restart instances that boot from Amazon EBS volumes while preserving state, with very fast start-up times. As with any use of Amazon EBS, you only pay for the amount of resources you consume."

For more detail on the EBS boot process, this is more-or-less required reading - See the section titled "Boot times" and "How You're Charged": http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?Concepts_BootFromEBS.html

Of particular note is that, "We charge a full instance hour for every transition from a stopped state to a running state, even if you transition the instance multiple times within a single hour." The following implies that this is only the case for EBS. This information is _deeply_buried_ - so, if you need to flick machines on and off frequently, boot-from-EBS could be more costly.

  • This seems to have changed. "When an Amazon EBS-backed instance is stopped, you're not charged for instance usage; however, you're still charged for volume storage. As soon as you start your instance, we charge a minimum of one minute for usage. After one minute, we charge only for the seconds used." – Robert Hensing May 31 '19 at 07:16
7

There is no definite answer to this because that's dependent on EC2's current load. You may also experience capacity issues. In my experience I get EC2 startups in about a minute to three for a Small in west-1b. I don't think Amazon even has an SLA to guarantee the ability to start new instances. Rackspace Cloud Server 256MB is also about a minute but I've seen about three minutes or so.

Rob Olmos
  • 2,220
  • 1
  • 15
  • 25
  • 1
    That's not too bad. Would having a reserved instance help with the unpredictability? – Tobu Sep 09 '10 at 22:53
  • 1
    @Tobu Amazon alludes to it on the site but the SLA doesn't appear to specifically state that. The "Unavailable" portion requires there be running instances. I would appreciate any correction to my understanding of this by anyone! – Rob Olmos Sep 09 '10 at 23:37
  • @Tobu Reserved instance wouldn't help. They have no meaning except in how you're billed. – ceejayoz Oct 01 '12 at 17:40
5

My benchmarks indicate a bootup time of about 45s. The XEN hypervisor is responsible for most of that.
The test measures from instance launch (pick AMI and launch new instance) to SSH connectivity. I use debian squeeze, built with my own bootstrapper (doesn't start gettys etc.).

You can test the bootup time with a benchmark script I created for that specific purpose.

andsens
  • 361
  • 4
  • 10
3

There are various ways you can speed up your instance boot times. The majority of the time is the OS loading and what you have your AMI configure to load at boot. I posted some guidance I received from AWS Support in another post:

https://stackoverflow.com/a/39298090/1806763

Community
  • 1
JD D
  • 151
  • 5