Machine Types

A machine type specifies a particular collection of virtualized hardware resources available to a virtual machine (VM) instance, including the memory size, virtual CPU count, and maximum persistent disk capability.

This guide describes the available machine types. To create a VM instance, see Creating and Starting an Instance. For the prices of machine types, see Machine type pricing.

Predefined machine types

Predefined machine types have a fixed collection of resources. To define your own machine type, see Custom machine types.

Predefined machine types are managed by Google Compute Engine and come in four classes as discussed in the following sections. To view a list of all available machine types, run the following Google Cloud Platform SDK command:

gcloud compute machine-types list

Standard machine types

Standard machine types are suitable for tasks that have a balance of CPU and memory needs. Standard machine types have 3.75 GB of RAM per virtual CPU.

Machine name Description Virtual CPUs1 Memory (GB) Max number of persistent disks (PDs)2 Max total PD size (TB)
n1-standard-1 Standard 1 CPU machine type with 1 virtual CPU and 3.75 GB of memory. 1 3.75 16 (32 in Beta) 64
n1-standard-2 Standard 2 CPU machine type with 2 virtual CPUs and 7.5 GB of memory. 2 7.50 16 (64 in Beta) 64
n1-standard-4 Standard 4 CPU machine type with 4 virtual CPUs and 15 GB of memory. 4 15 16 (64 in Beta) 64
n1-standard-8 Standard 8 CPU machine type with 8 virtual CPUs and 30 GB of memory. 8 30 16 (128 in Beta) 64
n1-standard-16 Standard 16 CPU machine type with 16 virtual CPUs and 60 GB of memory. 16 60 16 (128 in Beta) 64
n1-standard-324 Standard 32 CPU machine type with 32 virtual CPUs and 120 GB of memory. 32 120 16 (128 in Beta) 64
n1-standard-64(Beta),5 Standard 64 CPU machine type with 64 virtual CPUs and 240 GB of memory. 64 240 16 (128 in Beta) 64

1For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), or 2.2 GHz Intel Xeon E5 v4 (Broadwell).

2Persistent disk usage is charged separately from machine type pricing

432-core machine types are not available in Sandy Bridge zones.

564-core machine types are only available in Haswell and Broadwell zones.

High-memory machine types

High-memory machine types are ideal for tasks that require more memory relative to virtual CPUs. High-memory machine types have 6.50GB of RAM per virtual CPU.

Machine Name Description Virtual CPUs1 Memory (GB) Max number of persistent disks (PDs)2 Max total PD size (TB)
n1-highmem-2 High memory 2 CPU machine type with 2 virtual CPUs and 13 GB of memory. 2 13 16 (64 in Beta) 64
n1-highmem-4 High memory 4 CPU machine type with 4 virtual CPUs, and 26 GB of memory. 4 26 16 (64 in Beta) 64
n1-highmem-8 High memory 8 CPU machine type with 8 virtual CPUs and 52 GB of memory. 8 52 16 (128 in Beta) 64
n1-highmem-16 High memory 16 CPU machine type with 16 virtual CPUs and 104 GB of memory. 16 104 16 (128 in Beta) 64
n1-highmem-324 High memory 32 CPU machine type with 32 virtual CPUs and 208 GB of memory. 32 208 16 (128 in Beta) 64
n1-highmem-64(Beta),5 High memory 64 CPU machine type with 64 virtual CPUs and 416 GB of memory. 64 416 16 (128 in Beta) 64

1For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), or 2.2 GHz Intel Xeon E5 v4 (Broadwell).

2Persistent disk usage is charged separately from machine type pricing

432-core machine types are not available in Sandy Bridge zones.

564-core machine types are only available in Haswell and Broadwell zones.

High-CPU machine types

High-CPU machine types are ideal for tasks that require more virtual CPUs relative to memory. High-CPU machine types have 0.90 GB of RAM per virtual CPU.

Machine name Description Virtual CPUs1 Memory (GB) Max number of persistent disks (PDs)2 Max total PD size (TB)
n1-highcpu-2 High-CPU machine type with 2 virtual CPUs and 1.80 GB of memory. 2 1.80 16 (64 in Beta) 64
n1-highcpu-4 High-CPU machine type with 4 virtual CPUs and 3.60 GB of memory. 4 3.60 16 (64 in Beta) 64
n1-highcpu-8 High-CPU machine type with 8 virtual CPUs and 7.20 GB of memory. 8 7.20 16 (128 in Beta) 64
n1-highcpu-16 High-CPU machine type with 16 virtual CPUs and 14.4 GB of memory. 16 14.4 16 (128 in Beta) 64
n1-highcpu-324 High-CPU machine type with 32 virtual CPUs and 28.8 GB of memory. 32 28.8 16 (128 in Beta) 64
n1-highcpu-64(Beta),5 High-CPU machine type with 64 virtual CPUs and 57.6 GB of memory. 64 57.6 16 (128 in Beta) 64

1For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), or 2.2 GHz Intel Xeon E5 v4 (Broadwell).

2Persistent disk usage is charged separately from machine type pricing

432-core machine types are not available in Sandy Bridge zones.

564-core machine types are only available in Haswell and Broadwell zones.

Shared-core machine types

Shared-core machine types provide one virtual CPU that is allowed to run for a portion of the time on a single hardware hyper-thread on the host CPU running your instance. Shared-core instances can be more cost-effective for running small, non-resource intensive applications than standard, high- memory or high-CPU machine types.

f1-micro Bursting

f1-micro machine types offer bursting capabilities that allow instances to use additional physical CPU for short periods of time. Bursting happens automatically when your instance requires more physical CPU than originally allocated. During these spikes, your instance will opportunistically take advantage of available physical CPU in bursts. Note that bursts are not permanent and are only possible periodically.

Machine name Description Virtual CPUs Memory (GB) Max number of persistent disks (PDs)2 Max total PD size (TB)
f1-micro Micro machine type with 0.2 virtual CPU, 0.60 GB of memory, backed by a shared physical core. 0.2 0.60 4 (16 in Beta) 3
g1-small Shared-core machine type with 0.5 virtual CPU, 1.70 GB of memory, backed by a shared physical core. 0.5 1.70 4 (16 in Beta) 3

1For the n1 series of machine types, a virtual CPU is implemented as a single hardware hyper-thread on a 2.6 GHz Intel Xeon E5 (Sandy Bridge), 2.5 GHz Intel Xeon E5 v2 (Ivy Bridge), 2.3 GHz Intel Xeon E5 v3 (Haswell), or 2.2 GHz Intel Xeon E5 v4 (Broadwell).

2Persistent disk usage is charged separately from machine type pricing

432-core machine types are not available in Sandy Bridge zones.

564-core machine types are only available in Haswell and Broadwell zones.

Larger machine types

In 2017, Compute Engine will offer new machine types with up to 1TB of memory. These machine types are ideal for resource-intensive workloads and offer more options for demanding applications. Watch this page for updates or contact the sales team for more information.

Custom machine types

If none of the predefined machine types match your needs, you can independently specify the number of vCPUs and the amount of memory for your instance.

Custom machine types are ideal for the following scenarios:

  • Workloads that are not a good fit for the predefined machine types that are available to you.
  • Workloads that require more processing power or more memory, but don't need all of the upgrades that are provided by the next larger predefined machine type.

It costs slightly more to use a custom machine type than an equivalent predefined machine type, and there are still some limitations in the amount of memory and vCPUs you can select. Read Creating an Instance with a Custom Machine Type for all the details.

GPUs and machine types

You can attach GPU dies to any non-shared-core predefined machine type or custom machine type that you are able to create in a zone. However, instances with lower numbers of GPU dies are limited to a maximum number of vCPUs. In general, higher numbers of GPU dies allow you to create instances with higher numbers of vCPUs and system memory. See GPUs on Compute Engine for details.

What's next

Send feedback about...

Compute Engine Documentation