Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Difference between STOP instance and SUSPEND instance in Google Cloud Platform

I was created an instance in Google Cloud Platform. I use this instance 2 to 4 days in a week. So, I want to close my instance for rest of the days to save my billing charges. So, what is best option for me. Stop the instance or Suspend the instance? What is the difference between them?

like image 694
Sann Avatar asked Mar 22 '21 09:03

Sann


People also ask

How do I stop instances in Google Cloud Platform?

In the Google Cloud console, go to the Cloud SQL Instances page. To open the Overview page of an instance, click the instance name. Click Stop.

Does Google cloud charge for stopped instances?

A stopped instance does not incur charges, but all of the resources that are attached to the instance will still be charged. For example, you are charged for persistent disks and external IP addresses according to the price sheet, even if an instance is stopped.

What happens when you suspend a virtual machine?

When a virtual machine is suspended, the current state of the operating system, and applications is saved, and the virtual machine put into a suspended mode. When you resume the virtual machine, the operating system and applications continue from the same point you suspended the virtual machine.

What is an instance in Google Cloud Platform?

An instance is a virtual machine (VM) hosted on Google's infrastructure. You can create an instance or create a group of managed instances by using the Google Cloud console, the Google Cloud CLI, or the Compute Engine API.


1 Answers

Please have a look at the documentation Suspending and resuming an instance:

Suspending an instance differs from stopping an instance in the following ways:

  • Suspended instances preserve the guest OS memory, device state, and application state.
  • Google charges for the storage necessary to save instance memory.
  • You can only suspend an instance for up to 60 days. After 60 days, the instance is automatically moved to the TERMINATED state.

and at the article Stopping and starting an instance:

Instances that are in a TERMINATED state are not charged for per-second usage and do not count toward your regional CPU quota, so you can choose to stop instances that you are not using, saving you from being charged for instances that aren't active. After you are ready, you can come back and start the same instances again, with the same instance properties, metadata, and resources.

Your instances are not charged for per-second usage while in the TERMINATED state but any resources attached to the virtual machine, such as static IPs and persistent disks, are charged until they are deleted.

As a result, it's better to stop your VM instance, to avoid extra changes for keeping instance's memory.

In addition, please have a look at the article Save money by stopping and starting Compute Engine instances on schedule.

like image 80
Serhii Rohoza Avatar answered Oct 16 '22 06:10

Serhii Rohoza