{"id":7123,"date":"2021-09-17T10:13:57","date_gmt":"2021-09-17T03:13:57","guid":{"rendered":"http:\/\/gcloudvn.wam.vn\/tiet-kiem-chi-phi-voi-quan-ly-may-ao-tu-dong-va-suspend-resume\/"},"modified":"2023-07-11T11:38:43","modified_gmt":"2023-07-11T04:38:43","slug":"tiet-kiem-chi-phi-voi-quan-ly-may-ao-tu-dong-va-suspend-resume","status":"publish","type":"post","link":"https:\/\/gcloudvn.com\/en\/kienthuc\/tiet-kiem-chi-phi-voi-quan-ly-may-ao-tu-dong-va-suspend-resume\/","title":{"rendered":"Save costs with automatic virtual machine management and Suspend\/Resume"},"content":{"rendered":"

A key benefit of cloud computing is that you can easily create and delete computing resources, paying only for what you use. While <\/span>production virtual machines<\/span>\u00a0(VM) tends to run continuously, some machines are only needed when running <\/span>batch jobs<\/span>, while other machines like the environment <\/span>develop or test<\/span> Usually only used during business hours. Keeping virtual machines running when they have no users or tasks to run serves no useful purpose, so shutting them down saves money.<\/span><\/p>\n

However, manually managing groups of virtual machines can be tedious, error-prone, and difficult to implement in a large organization. Furthermore, systems are migrated from <\/span>on-premises hardware <\/span>\u00a0often fail to take advantage of shutdown capabilities when they have no users or no tasks to run. In spite of <\/span>on-premises hardware<\/span> with or without, virtual machines in the cloud may be running, suspended, stopped, or turned into <\/span>machine images<\/span>, ready to recreate immediately. Each of these options has different costs and benefits.<\/span><\/p>\n

\"Save<\/p>\n

New Google Guide, <\/span>Optimize costs through automated virtual machine management<\/span><\/a>, which takes you through various ways to control the group <\/span>Compute Engine<\/a> VMs<\/span> yours, simple words <\/span>time-based scheduling<\/span> come take advantage <\/span>\u00a0<\/span>Recommender<\/span> parse to resize <\/span>underused VMs<\/span> and shutdown <\/span>idling ones<\/span>. You can learn about different approaches to running <\/span>batch jobs <\/span>effectively, from<\/span> self-deleting virtual machines<\/span> to organize simple or complex tasks with <\/span>Workflows<\/span> or <\/span>Cloud Composer<\/span> and reduce operating system maintenance costs with <\/span>VM Manager<\/span>.<\/span><\/p>\n

This guide also covers the difference between suspending, stopping, and deleting instances. With feature <\/span>suspend and resume<\/span><\/a>, now in Preview, you have a cost-effective way to "pause" an instance while preserving its memory and application state, the same way a laptop remembers what you are doing when you close the lid. Once the instance is resumed, your users can resume their work from right where they left off without having to wait for the instance to start or load their software.<\/span><\/p>\n

Start by taking a look <\/span>decision tree<\/span> in <\/span>Optimize costs through automated virtual machine management<\/span> and contact Gimasys for advice on Google Cloud:<\/span><\/p>\n