The memory-optimized machine family provides the most compute and memoryresources of any Compute Engine machine family offering. They areideal for workloads that require higher memory-to-vCPU ratios than thehigh-memory machine types in the general-purpose machine series.

• The X4 machine series offers bare metal instances with 6 to 32 TB ofmemory.
• The M4 machine series offers VM instances with up to 6 TB of memory.
• The M3 machine series offers VM instances with 1 to 4 TB of memory.
• The M2 machine series offers VM instances with up to 12 TB of memory.
• The M1 machine series offers VM instances with up to 4 TB of memory.

These machine series are well-suited for large in-memory databases such as SAPHANA, as well as online analytical processing (OLAP) and in-memory dataanalytics workloads.

The X4, M4, M3, M2, and M1 machine series offer the lowest cost per GB of memoryon Compute Engine, making them a great choice for workloads that utilizehigher memory configurations with low compute resources requirements.Additionally, M2 and M1 offer savings of up to 30% with sustained use discounts.X4, M4, M3, M2, and M1 are eligible forresource-based committed use discounts (CUDs),that bring savings of greater than 60% in exchange for 3-year commitments.

Machine series	Workloads
X4 machine series	Extra large SAP HANA systems On-demand, enterprise grade, ultra memory-equipped IaaS High performance computing
M4 machine series	OLAP and OLTP SAP workloads Memory intensive applications, such as genomic modeling and electronic design automation Small to medium in-memory databases such as SAP HANA High performance computing
M3 machine series	OLAP and OLTP SAP workloads Memory intensive applications, such as genomic modeling and electronic design automation High performance computing
M2 machine series	Large in-memory databases such as SAP HANA In-memory databases and in-memory analytics, business warehousing (BW) workloads, genomics analysis, SQL analysis services
M1 machine series	Medium in-memory databases such as SAP HANA Tasks that require intensive use of memory with higher memory-to-vCPU ratios than the general-purpose high-memory machine types. In-memory databases and in-memory analytics, business warehousing (BW) workloads, genomics analysis, SQL analysis services. Microsoft SQL Server and similar databases.

X4 machine series

The X4 machine series offers more storage and networking options to support yourmost demanding workloads. The X4 machine series offers six predefined machinetypes. These machine types provide you with the capability to provision baremetal instances with up to 1,920 vCPUs and up to 32 TB of RAM.

X4 instances are powered by the 4th generation Intel Xeon Scalable processors(code-named Sapphire Rapids) andTitanium.X4 instances use only the NVMe disk interface for storage, andonly useGoogle Cloud Hyperdisk storage. X4instances use a version of the IntelInfrastructure Data Plane Function (IDPF) driverthat has been optimized for use with Google Cloud. VirtIO-net, gVNIC, and SCSIinterfaces are not supported.

X4 instances give you access to the raw compute resources of the server. Baremetal instances also provide access to several on-board, function-specificaccelerators and offloads:

• Intel QuickAssist Technology (QAT): 1 accelerator
• Intel Dynamic Load Balancer (DLB): 1 accelerator
• Intel Data Streaming Accelerator (DSA): up to 4 accelerators
• Intel In-Memory Analytics Accelerator (IAA): up to 4 accelerators

To move your workload from a VM instance to an X4 bare metal instance, seeMove your workload to a new compute instance.

Contact yourGoogle Cloud account manager forpricing and ordering information for X4, or to discuss on-demand pricing fortesting X4 instances.

When purchasingresource-based commitmentsfor X4 machine types, note that the commitment type is separate for each X4machine type.

X4 Limitations

The X4 machine series is only available as predefined machine types. Custommachine shapes are not available. The following additional restrictions apply:

• You can't attach Persistent Disk volumes to an X4 instance, onlyHyperdisk volumes.
• The X4 machine series is available in onlyselect zones and regions.
• X4 instances aren't supported with all operating system images. Theoperating system details page shows whichoperating system versions can be used with X4 instances.
• If using a custom image, when you create the image, you must enable theUEFI-compatible OSfeature.
• Shielded VM isn't supportedwith bare metal instances.
• Live migration is not supported with X4 instances.
• There's no hypervisor provided with X4 bare metal instances andnestedvirtualizationisn't enabled.
• X4 machine series instances can take up to 30 mins to boot due to largehardware and the Power-On Self-Test (POST).
• The interactive serial console is not available for the X4 machine series. Formore information, seeTroubleshooting using the serial console.

X4 machine types

Machine types	vCPUs1	Memory (GB)	Local SSD	Default egress bandwidth (Gbps)2	Tier_1 egress bandwidth (Gbps)
x4-480-6t-metal	480	6,144	Not available	Up to 100	Not available
x4-480-8t-metal	480	8,192	Not available	Up to 100	Not available
x4-960-12t-metal	960	12,288	Not available	Up to 100	Not available
x4-960-16t-metal	960	16,384	Not available	Up to 100	Not available
x4-1440-24t-metal	1,440	24,576	Not available	Up to 100	Not available
x4-1920-32t-metal	1,920	32,768	Not available	Up to 100	Not available

Supported disk types for X4

X4 machine types support the following block storage options:

• Hyperdisk Balanced (hyperdisk-balanced)
• Hyperdisk Extreme (hyperdisk-extreme)

For disks attached to an X4 instance:

• The number of Google Cloud Hyperdisk volumes can't exceed 8 Hyperdisk Extreme or 32 Hyperdisk Balancedper instance. The total number of Google Cloud Hyperdisk volumes can't exceed 32per instance.
• The maximum total disk capacity (in TiB) across all disk types can't exceed512 TiB.

For details about the capacity limits, seeHyperdisk capacity limits per VM.

X4 storage limits are described in the following table:

Maximum number of disks
Machine types	Google Cloud Hyperdisk per VM	Hyperdisk Balanced	Hyperdisk Throughput	Hyperdisk Extreme
x4-480-6t-metal	32	32	Not supported	8
x4-480-8t-metal	32	32	Not supported	8
x4-960-12t-metal	32	32	Not supported	8
x4-960-16t-metal	32	32	Not supported	8
x4-1440-24t-metal	32	32	Not supported	8
x4-1920-32t-metal	32	32	Not supported	8

Network support for X4 instances

X4 bare metal instances require theIntel IDPF LAN PF device driver.X4 supports up to 100 Gbps network bandwidth for standardnetworking. The gVNIC network interface isn't supported with bare metalinstances.

Before migrating to X4 or creating X4 instances,make sure that theoperating system imagethat you use supports the IDPF network driver. If you create an X4instance with an operating system that doesn't support the IDPF driver, thenyou might not be able to connect to the instance.

Maintenance experience for X4 instances

During thelifecycle of aCompute Engine instance, the host machine that your instance runs on undergoes multiplehost events.A host event can include the regular maintenance ofCompute Engine infrastructure, or in rare cases, a host error. Compute Engine alsoapplies some non-disruptive lightweight upgrades for the hypervisor and networkin the background.

The X4 machine series offers the following features related to hostmaintenance:

Machine type	Typical scheduled maintenance event frequency	Maintenance behavior	Advanced notification	On-demand maintenance	Simulate maintenance
All machine types	Minimum of 90 days	Restart in place	60 days	Yes	Yes

The maintenance frequencies shown in the previous table are approximations, not guarantees.Compute Engine might occasionally perform maintenance more frequently.

X4 also lets you perform maintenance for unplanned emergent maintenance eventswithin a short window of time.Emergent maintenance events are typically needed to address security,hardware, or software issues of medium to high severity that have a highpotential for causing outages. These maintenance events are deemed importantand time-sensitive, but not critical enough to require an immediate outage toperform the maintenance. Emergent maintenance events have thefollowing features for X4 machine types:

• Advanced notification: 14 days
• Maintenance behavior: Restart in place

During emergent maintenance maintenance, X4 instances are moved to a different,healthy host.

For emergent maintenance events, you canmanually start the maintenanceat any time within the 14 day advance notification period. If you don'tmanually start the maintenance operation within the 14-day period, then themaintenance starts automatically at the end of the advanced notification period.

M4 machine series

The M4 machine series offers machine types that are suitable for OLTP and OLAPworkloads running on SAP HANA. These machine types allow you to provision up to224 vCPUs and up to 6 TB of RAM.M4 instances use only NVMe for storage, and supportHyperdisk Balanced andHyperdisk Extreme. M4 instances useonlygVNIC for networking.VirtIO-net and SCSI interfaces are not supported.

M4 instances support resource-based CUDs, Spot VMs, and reservations,as well as performance monitoring unit (PMU), and compact placement policies.

Resource-based CUDs for M4 instances are available under two separatecommitment types, each applying to specific machine types. When you purchase acommitment, ensure that you select the correct commitment type, as follows:

• Form4-ultramem-224 (6 TB), selectMemory-optimized M4 6TB as thecommitment type in the Google Cloud console.
• For any other M4 machine type, selectMemory-optimized M4 as thecommitment type in the Google Cloud console.
• If you use gcloud CLI or REST to purchase commitments,see theresource-based CUDs documentationfor the commitment type values to use.

M4 machine types

Machine types	vCPUs	Memory (GB)	Default egress bandwidth (Gbps)1	Tier_1 egress bandwidth (Gbps)2
m4-hypermem-16	16	248	Up to 16	Not available
m4-hypermem-32	32	496	Up to 32	Not available
m4-hypermem-64	64	992	Up to 32	Not available
m4-megamem-28	28	372	Up to 32	Not available
m4-megamem-56	56	744	Up to 32	Not available
m4-megamem-112	112	1,488	Up to 50	Not available
m4-megamem-224	224	2,976	Up to 100	Not available
m4-ultramem-56	56	1,488	Up to 32	Not available
m4-ultramem-112	112	2,976	Up to 50	Not available
m4-ultramem-224	224	5,952	Up to 100	Not available

Supported disk types for M4

M4 machine types support the following block storage options:

• Hyperdisk Balanced (hyperdisk-balanced)
• Hyperdisk Extreme (hyperdisk-extreme)

M4 machine types support only the NVMe disk interface.

M4 instances don't support Persistent Disk or Local SSD.ReadMove your workload from an existing VM to a new VMto migrate your Persistent Disk resources to a newer machine series.

Disk and capacity limits

You can attach a mixture of different Hyperdisk types toan instance, but the maximum total disk capacity (in TiB) across all disktypes can't exceed:

• For machine types with less than 32 vCPUs: 257 TiB for all Hyperdisk

• For machine types with 32 or more vCPUs: 512 TiB for all Hyperdisk

For details about the capacity limits, seeHyperdisk size and attachment limits.

M4 instance storage limits are described in the following table:

	Maximum number of disks
Machine types	Hyperdisk per VM	Hyperdisk Balanced	Hyperdisk Throughput	Hyperdisk Extreme	Local SSD
m4-hypermem-16	16	16	0	0	Not supported
m4-hypermem-32	32	32	0	0	Not supported
m4-hypermem-64	32	32	0	8	Not supported
m4-megamem-28	32	32	0	0	Not supported
m4-megamem-56	32	32	0	0	Not supported
m4-megamem-112	64	64	0	8	Not supported
m4-ultramem-56	32	32	0	0	Not supported
m4-ultramem-112	64	64	0	8	Not supported
m4-ultramem-224	128	128	0	8	Not supported

Network support for M4 instances

M4 instances requiregVNIC network interfaces.M4 instances support up to 100 Gbps network bandwidth for standardnetworking and don't support per VM Tier_1 networking performance.

Before migrating to M4 or creating M4 VMinstances, make sure that theoperating system imagethat you use supports the gVNIC driver for VM instances.These images include anupdated gVNIC driver, even if the guest OS shows thegve driver version as1.0.0. If your M4 VM isusing an operating system with an older version of gVNIC driver, this is stillsupported but the VM might experience suboptimal performance such as lessnetwork bandwidth or higher latency.

If you use a custom OS image to create a M4 VM, you canmanually install the most recent gVNIC driver.The gVNIC driver version v1.4.2 or later is recommended for use with M4VMs. Google recommends using the latest gVNIC driver version to benefit fromadditional features and bug fixes.

M4 Limitations

The M4 machine series is only available as predefined machine types. Custommachine shapes are not available. The M4 instances are available in onlyselect zones and regions.

Maintenance experience for M4 instances

During thelifecycle of aCompute Engine instance, the host machine that your instance runs on undergoes multiplehost events.A host event can include the regular maintenance ofCompute Engine infrastructure, or in rare cases, a host error. Compute Engine alsoapplies some non-disruptive lightweight upgrades for the hypervisor and networkin the background.

The M4 machine series offers the following features related to hostmaintenance:

Machine type	Typical scheduled maintenance event frequency	Maintenance behavior	Advanced notification	On-demand maintenance	Simulate maintenance
All machine types	Monthly	Live migrate	7 days	Yes	Yes

The maintenance frequencies shown in the previous table are approximations, not guarantees.Compute Engine might occasionally perform maintenance more frequently.

M3 machine series

The M3 machine series introduces two new OLAP shapes for 2 TiB and1 TiB SAP HANA systems. These machine types allow you to provision up to128 vCPUs and up to 4 TB of RAM. M3 instances use only NVMe for storage,and supportHyperdisk Balanced storage. M3 machinesuse onlygVNIC for networking.VirtIO-net and SCSI interfaces are not supported.

Pricing for these instances per vCPUhour and per GB of memory is similar to the pricing for M1 instances. Disk usageand network usage is charged separately from machine type pricing.For details, seeDisk and imagepricing andNetwork pricing.

M3 instances support resource-based CUDs, Spot VMs, andreservations, as well as compact placement policies. The commitment type thatyou must use to purchase M3 instances is separate from the one for M1 or M2instances. You can purchase a single commitment to cover both M1 and M2instances, but you can't group M3 instances in that commitment. For moreinformation, see theCommitment typessection for resource-based commitments.

To update a current instance to use the M3 machine series, seeMove your workload to a new compute instance.

M3 machine types

Machine types	vCPUs	Memory (GB)	Default egress bandwidth (Gbps)1	Tier_1 egress bandwidth (Gbps)2
m3-ultramem-32	32	976	Up to 32	Not supported
m3-ultramem-64	64	1,952	Up to 32	Up to 50
m3-ultramem-128	128	3,904	Up to 32	Up to 100
m3-megamem-64	64	976	Up to 32	Up to 50
m3-megamem-128	128	1,952	Up to 32	Up to 100

Supported disk types for M3

M3 machine types support the following block storage options:

• Zonal balanced Persistent Disk (pd-balanced)
• Zonal SSD (performance) Persistent Disk (pd-ssd)
• Extreme Persistent Disk (pd-extreme)
• Hyperdisk Balanced (hyperdisk-balanced)
• Hyperdisk Balanced High Availability (hyperdisk-balanced-high-availability)
• Hyperdisk Extreme (hyperdisk-extreme)
• Hyperdisk Throughput (hyperdisk-throughput)
• Local SSD

M3 machine types support only the NVMe disk interface.

Disk and capacity limits

If supported by the machine type, you can attach a mixture ofHyperdisk and Persistent Disk volumes to an instance, but the followingrestrictions apply:

• The combined number of both Hyperdisk and Persistent Disk volumes can't exceed 128 per instance.

• The maximum total disk capacity (in TiB) across all disk types can't exceed:

  • For machine types with less than 32 vCPUs:

    • 257 TiB for all Hyperdisk or all Persistent Disk
    • 257 TiB for a mixture of Hyperdisk and Persistent Disk

  • For machine types with 32 or more vCPUs:

    • 512 TiB for all Hyperdisk
    • 512 TiB for a mixture of Hyperdisk and Persistent Disk
    • 257 TiB for all Persistent Disk

For details about the capacity limits, see Hyperdisk size and attachment limits andPersistent Disk maximum capacity.

M3 storage limits are described in the following table:

	Maximum number of disks
Machine types	Per VM1	Hyperdisk per VM	Hyperdisk Balanced	Hyperdisk Throughput	Hyperdisk Extreme	Local SSD
m3-ultramem-32	128	64	32	64	0	4 or 8
m3-ultramem-64	128	64	32	64	8	4 or 8
m3-ultramem-128	128	64	32	64	8	8
m3-megamem-64	128	64	32	64	8	4 or 8
m3-megamem-128	128	64	32	64	8	8

Network support for M3 instances

M3 instances requiregVNIC network interfaces.M3 instances support up to 32 Gbps network bandwidth for standardnetworking and up to 100 Gbps network bandwidth per VM Tier_1 networking performance.

Before migrating to M3 or creating M3 VMinstances, make sure that theoperating system imagethat you use supports the gVNIC driver for VM instances.These images include anupdated gVNIC driver, even if the guest OS shows thegve driver version as1.0.0. If your M3 VM isusing an operating system with an older version of gVNIC driver, this is stillsupported but the VM might experience suboptimal performance such as lessnetwork bandwidth or higher latency.

If you use a custom OS image to create a M3 VM, you canmanually install the most recent gVNIC driver.The gVNIC driver version v1.4.2 or later is recommended for use with M3VMs. Google recommends using the latest gVNIC driver version to benefit fromadditional features and bug fixes.

M3 Limitations

The M3 machine series is only available as predefined machine types. Custommachine shapes are not available. The following additional restrictions apply:

• You can't useregional Persistent Diskwith the M3 machine series.
• The M3 machine series is available in onlyselect zones and regions.
• M3 instances aren't available with all operating system images. Theoperating system details page shows whichoperating system versions can be used with M3 instances.
• The M3 machine series doesn't support standard Persistent Disk(pd-standard).
• The ability to add or resize a Persistent Disk for a running M3 instance doesn'twork as expected on Windows Server 2016 or Windows Server 2012 R2 operatingsystems. For more information, seeGeneric disk error on Windows Server 2016 and 2012 R2 for M3 VMs.

Maintenance experience for M3 instances

During thelifecycle of aCompute Engine instance, the host machine that your instance runs on undergoes multiplehost events.A host event can include the regular maintenance ofCompute Engine infrastructure, or in rare cases, a host error. Compute Engine alsoapplies some non-disruptive lightweight upgrades for the hypervisor and networkin the background.

The M3 machine series offers the following features related to hostmaintenance:

Machine type	Typical scheduled maintenance event frequency	Maintenance behavior	Advanced notification	On-demand maintenance	Simulate maintenance
All machine types	Minimum of 30 days	Live migrate	7 days	Yes	Yes

The maintenance frequencies shown in the previous table are approximations, not guarantees.Compute Engine might occasionally perform maintenance more frequently.

M2 machine series

With 6 TiB, 9 TiB, and 12 TiB machine types in theM2 machine series, SAP customers can run their largest SAP HANA databases onGoogle Cloud.

The M2 series is available with on-demand and spot pricing for anevaluation period only. Long running usage requires purchasing a resource-basedcommitment. For more information, see theVM pricing page.Disk usage and network usage is charged separately from machine type pricing.For details, seeDisk and imagepricing andNetwork pricing.

M2 instances support resource-based CUDs, Spot VMs, reservations,and compact placement policies.

M2 machine types

Machine types	vCPUs1	Memory (GB)	Default egress bandwidth (Gbps)2
m2-ultramem-208	208	5,888	Up to 323
m2-ultramem-416	416	11,776	Up to 323
m2-megamem-416	416	5,888	Up to 323
m2-hypermem-416	416	8,832	Up to 323

Supported disk types for M2

M2 machine types can use the following block storage options:

• Zonal balanced Persistent Disk (pd-balanced)
• Zonal SSD (Performance) Persistent Disk (pd-ssd)
• Extreme Persistent Disk (pd-extreme)
• Hyperdisk Balanced (hyperdisk-balanced)
• Hyperdisk Extreme (hyperdisk-extreme)

If supported by the machine type, you can attach a mixture ofHyperdisk and Persistent Disk volumes to an instance, but the followingrestrictions apply:

• The combined number of both Hyperdisk and Persistent Disk volumes can't exceed 128 per instance.

• The maximum total disk capacity (in TiB) across all disk types can't exceed:

  • For machine types with less than 32 vCPUs:

    • 257 TiB for all Hyperdisk or all Persistent Disk
    • 257 TiB for a mixture of Hyperdisk and Persistent Disk

  • For machine types with 32 or more vCPUs:

    • 512 TiB for all Hyperdisk
    • 512 TiB for a mixture of Hyperdisk and Persistent Disk
    • 257 TiB for all Persistent Disk

For details about the capacity limits, see Hyperdisk size and attachment limits andPersistent Disk maximum capacity.

M2 storage limits are described in the following table:

	Maximum number of disks
Machine types	Per VM1	Hyperdisk per VM	Hyperdisk Balanced	Hyperdisk Throughput	Hyperdisk Extreme	Local SSD
m2-ultramem-208	128	64	32	0	8	Not supported
m2-ultramem-416	128	64	32	0	8	Not supported
m2-megamem-416	128	64	32	0	8	Not supported
m2-hypermem-416	128	64	32	0	8	Not supported

M2 Limitations

The M2 machine series is available only as predefined machine types.This series offers from 14 GB to 28 GB memory per vCPU. Thefollowing restrictions apply:

• The M2 machine series is available in onlyselect zones and regions on specificCPU processors.
• You can't useregional Persistent Diskwith the M2 machine series.
• The M2 machine series uses only the SCSI interface for attached disks.
• Sole tenant nodes are available foronly them2-ultramem-416 shape.

Maintenance experience for M2 instances

During thelifecycle of aCompute Engine instance, the host machine that your instance runs on undergoes multiplehost events.A host event can include the regular maintenance ofCompute Engine infrastructure, or in rare cases, a host error. Compute Engine alsoapplies some non-disruptive lightweight upgrades for the hypervisor and networkin the background.

The M2 machine series offers the following features related to hostmaintenance:

Machine type	Typical scheduled maintenance event frequency	Maintenance behavior	Advanced notification	On-demand maintenance	Simulate maintenance
All machine types	Minimum of 30 days	Live migrate	7 days	Yes	Yes

The maintenance frequencies shown in the previous table are approximations, not guarantees.Compute Engine might occasionally perform maintenance more frequently.

M1 machine series

The M1 machine series is the older generation memory-optimized machine seriesthat offers 14.9 to 24 GB of memory per vCPU. This series offers them1-ultramem andm1-megamem machine types and are only available in specificregions and zones.

Note:The prefix in the following machine names changed from "n1" to "m1" to more clearly identify the machines as members of the memory-optimized machine family:

• n1-megamem-96 is nowm1-megamem-96
• n1-ultramem-40 is nowm1-ultramem-40
• n1-ultramem-80 is nowm1-ultramem-80
• n1-ultramem-160 is nowm1-ultramem-160

The machines themselves did not change and the former names are still supported as aliases for these machines.

For details on pricing, see theVM pricing page.Disk usage and network usage is charged separately from machine type pricing.For more information, seeDisk and imagepricing andNetwork pricing.

M1 instances support resource-based CUDs, Spot VMs, reservations,and compact placement policies.

M1 machine types

Machine types	vCPUs1	Memory (GB)	Default egress bandwidth (Gbps)2
m1-ultramem-40	40	961	Up to 32
m1-ultramem-80	80	1922	Up to 32
m1-ultramem-160	160	3844	Up to 32
m1-megamem-96	96	1433.6	Up to 32

Supported disk types for M1

M1 machine types can use the following block storage options:

• Zonal balanced Persistent Disk (pd-balanced)
• Zonal SSD (Performance) Persistent Disk (pd-ssd)
• Extreme Persistent Disk (pd-extreme)
• Hyperdisk Balanced (hyperdisk-balanced)
• Hyperdisk Extreme (hyperdisk-extreme)
• Local SSD

If supported by the machine type, you can attach a mixture ofHyperdisk and Persistent Disk volumes to an instance, but the followingrestrictions apply:

• The combined number of both Hyperdisk and Persistent Disk volumes can't exceed 128 per instance.

• The maximum total disk capacity (in TiB) across all disk types can't exceed:

  • For machine types with less than 32 vCPUs:

    • 257 TiB for all Hyperdisk or all Persistent Disk
    • 257 TiB for a mixture of Hyperdisk and Persistent Disk

  • For machine types with 32 or more vCPUs:

    • 512 TiB for all Hyperdisk
    • 512 TiB for a mixture of Hyperdisk and Persistent Disk
    • 257 TiB for all Persistent Disk

For details about the capacity limits, see Hyperdisk size and attachment limits andPersistent Disk maximum capacity.

M1 storage limits are described in the following table:

	Maximum number of disks
Machine types	Per VM1	Hyperdisk per VM	Hyperdisk Balanced	Hyperdisk Throughput	Hyperdisk Extreme	Local SSD
m1-ultramem-40	128	64	32	0	0	5
m1-ultramem-80	128	64	32	0	8	8
m1-ultramem-160	128	64	32	0	8	Not supported
m1-megamem-96	128	64	32	0	8	Not supported

M1 Limitations

The M1 machine series is only available as predefined machine types.This series offers 14 GB to 28 GB of memory per vCPU. Thefollowing restrictions apply:

• You can't useregional Persistent Diskwith the M1 series.
• M1 instances are only available inselect zones and regions on specificCPU processors.

Maintenance experience for M1 instances

During thelifecycle of aCompute Engine instance, the host machine that your instance runs on undergoes multiplehost events.A host event can include the regular maintenance ofCompute Engine infrastructure, or in rare cases, a host error. Compute Engine alsoapplies some non-disruptive lightweight upgrades for the hypervisor and networkin the background.

The M1 machine series offers the following features related to hostmaintenance:

Machine type	Typical scheduled maintenance event frequency	Maintenance behavior	Advanced notification	On-demand maintenance	Simulate maintenance
All machine types	Minimum of 30 days	Live migrate	7 days	Yes	Yes

The maintenance frequencies shown in the previous table are approximations, not guarantees.Compute Engine might occasionally perform maintenance more frequently.

What's next

• Creating and starting a virtual machine instance
• Learn about the differentStorage options for yourinstance.
• Move your workload to a new compute instance
• Using Google Virtual NIC
• VM instance pricing