Article complete

Google Cloud makes Suspend/Resume generally available for cost optimisation

Storage is dynamically provisioned when Suspend is requested and is separate from the instance’s boot disk.

A laptop with cloud icons and folders labeled "SUSPEND" and "RESUME" against a colorful sky and clouds background.

Key takeaways

  • Google Cloud's suspend/resume feature offers enhanced control over resource consumption for users.
  • Suspending a VM saves its state to disk, allowing users to resume later without incurring full running costs.
  • Users only pay for storage costs when a VM is suspended, significantly reducing expenses compared to active instances.
  • The feature supports a wide range of operating systems, increasing compatibility without needing cloud-specific images.
  • Storage is dynamically provisioned separately from the boot disk, optimising resource usage and costs.

Takeaways drafted with AI from the article text.

How it works

Suspending an instance sends an ACPI S3 signal to the instance’s operating system leading to two significant advantages compared to similar functionalities from other cloud providers. 

  1. Broad compatibility with a wide selection of OS images without requiring you to use a cloud-specific OS image or install daemons. Undocumented and custom OS images that respond to the ACPI S3 signal may also work with Suspend. 
  2. Storage is dynamically provisioned when Suspend is requested and is separate from the instance’s boot disk. This is in contrast to implementations in other clouds that require you to ensure that you have sufficient empty space in your boot disk to save the instance state which may increase the running costs of your VM. This also ensures that your suspended instance only consumes as much storage as it needs

Published

Spotted an error? Tell our editors. Read our editorial standards and corrections.