General-purpose machine family for Compute Engine


This document describes the features of the Compute Engine general-purpose machine family. The general-purpose machine family has the best price-performance with the most flexible vCPU to memory ratios, and provides features that target most standard and cloud-native workloads.

The general-purpose machine family has predefined and custom machine types to align with your workload, depending on your requirements. E2, E2 shared-core, N2, N2D, and Tau T2D are second generation machine series in this family; N1 and its related shared-core machine types are first generation machine series. The newest generation, C3, is powered by 4th generation Intel Xeon Scalable processors and offers a sustained, all-core turbo frequency of 3.0 GHz, 8 channels of DDR5 memory, and up to 200 Gbps per VM Tier_1 networking performance.

Machine series Workloads
C3, C3D
  • High traffic web, app and ad servers
  • Databases and caches
  • Game servers
  • Data analytics
  • Media streaming and transcoding
  • Network appliances
  • CPU-based ML training and inference
E2
  • Low-traffic web servers
  • Back office apps
  • Containerized microservices
  • Small databases
  • Virtual desktops
  • Development and test environments
N2, N2D, Tau T2D, N1
  • Low to medium traffic web and application servers
  • Containerized microservices
  • Business intelligence applications
  • Virtual desktops
  • CRM applications
  • Data pipelines
Tau T2A
  • Scale-out workloads
  • Web servers
  • Containerized microservices
  • Media transcoding
  • Large-scale Java applications

To learn how your selection affects the performance of Persistent Disk volumes attached to your VMs, see Configure your persistent disks and VMs.

C3D machine series

C3D VMs are powered by the 4th generation AMD EPYC™ (Genoa) processor with a maximum frequency of 3.7 Ghz. C3D machine types are optimized for the underlying hardware architecture to deliver optimal, reliable, and consistent performance.

C3D uses Google's custom IPU, which enables higher levels of networking performance, isolation and security. The C3D machine series supports a default network bandwidth of up to 100 Gbps and up to 200 Gbps per VM Tier_1 networking performance.

In summary, the C3D machine series:

  • Is powered by 4th generation AMD EPYC™ processor and Google's IPU.
  • Supports up to 360 vCPUs and 2,880 GB of DDR5 memory.
  • Supports standard network configuration with up to 100 Gbps bandwidth and Tier_1 networking with up to 200 Gbps bandwidth.
  • Supports the following discount and consumption options:

C3D machine types

C3D VMs are available in standard, highcpu, highmem, and lssd configurations in sizes ranging from 4 to 360 vCPUs and up to 2,880 GB of memory. The highcpu configuration offers the lowest price per performance for compute-bound workloads that do not require large amounts of memory.

C3D standard

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3d-standard-4 4 16 up to 20 N/A
c3d-standard-8 8 32 up to 20 N/A
c3d-standard-16 16 64 up to 20 N/A
c3d-standard-30 30 120 up to 20 up to 50
c3d-standard-60 60 240 up to 40 up to 75
c3d-standard-90 90 360 up to 60 up to 100
c3d-standard-180 180 720 up to 100 up to 150
c3d-standard-360 360 1,440 up to 100 up to 200

* A CPU uses two threads per core, and a vCPU respresents a single thread. See CPU platforms.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3D highcpu

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3d-highcpu-4 4 8 up to 20 N/A
c3d-highcpu-8 8 16 up to 20 N/A
c3d-highcpu-16 16 32 up to 20 N/A
c3d-highcpu-30 30 59 up to 20 up to 50
c3d-highcpu-60 60 118 up to 40 up to 75
c3d-highcpu-90 90 177 up to 60 up to 100
c3d-highcpu-180 180 354 up to 100 up to 150
c3d-highcpu-360 360 708 up to 100 up to 200

* A CPU uses two threads per core, and a vCPU respresents a single thread. See CPU platforms.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3D highmem

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3d-highmem-4 4 32 up to 20 N/A
c3d-highmem-8 8 64 up to 20 N/A
c3d-highmem-16 16 128 up to 20 N/A
c3d-highmem-30 30 240 up to 20 up to 50
c3d-highmem-60 60 480 up to 40 up to 75
c3d-highmem-90 90 720 up to 60 up to 100
c3d-highmem-180 180 1,440 up to 100 up to 150
c3d-highmem-360 360 2,880 up to 100 up to 200

* A CPU uses two threads per core, and a vCPU respresents a single thread. See CPU platforms.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3D with Local SSD

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3d-standard-8-lssd 8 32 Up to 20 N/A
c3d-standard-16-lssd 16 64 Up to 20 N/A
c3d-standard-30-lssd 30 120 Up to 20 up to 50
c3d-standard-60-lssd 60 240 Up to 40 up to 75
c3d-standard-90-lssd 90 360 Up to 60 up to 100
c3d-standard-180-lssd 180 720 Up to 100 up to 150
c3d-standard-360-lssd 360 1440 Up to 100 up to 200

* A CPU uses two threads per core, and a vCPU respresents a single thread. See CPU platforms.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3D doesn't support custom machine types.

Supported disk types for C3D

C3D VMs support only the NVMe disk interface and can use the following block storage types:

  • Balanced Persistent Disk (pd-balanced)
  • SSD (performance) Persistent Disk (pd-ssd)
  • Hyperdisk Throughput (hyperdisk-throughput)
  • Local SSD (only available with -lssd machine types)

To use Local SSD with C3D, create your VM using the -lssd variant of the C3D machine types. Selecting this machine type creates a VM of the specified size with Local SSD partitions attached. You must use a c3d-standard-*-lssd machine type to use Local SSD with your VM; you can't attach Local SSD volumes separately.

Disk and capacity limits

You can use a mixture of Persistent Disk and Hyperdisk volumes with a VM, but the following restrictions apply.

  • The combined number of both Hyperdisk and Persistent Disk volumes can't exceed 128.
  • The total capacity of all Persistent Disk volumes can't exceed 257 TiB.
  • The number of Hyperdisk volumes of all types that you can attach to a VM can't exceed the limits stated in the Max number of Hyperdisk volumes column in the following table. For details about these limits, see Hyperdisk capacity.

Local SSD disks are not included in any of the aforementioned limits.

C3D standard

Machine types Max number of disks per VM,
across all disks*
Max number of
Hyperdisk
volumes
Max total disk size (TB)
across all disks
Local SSD support
c3d-standard-4 128 24 257 Not supported
c3d-standard-8 128 32 257 Not supported
c3d-standard-16 128 48 257 Not supported
c3d-standard-30 128 64 257 Not supported
c3d-standard-60 128 64 512 Not supported
c3d-standard-90 128 64 512 Not supported
c3d-standard-180 128 64 512 Not supported
c3d-standard-360 128 64 512 Not supported

C3D highcpu

Machine types Max number of disks per VM,
across all disks*
Max total disk size (TB)
across all disks
Max number of
Hyperdisk
volumes
Local SSD
c3d-highcpu-4 128 257 24 Not supported
c3d-highcpu-8 128 257 32 Not supported
c3d-highcpu-16 128 257 48 Not supported
c3d-highcpu-30 128 257 64 Not supported
c3d-highcpu-60 128 512 64 Not supported
c3d-highcpu-90 128 512 64 Not supported
c3d-highcpu-180 128 512 64 Not supported
c3d-highcpu-360 128 512 64 Not supported

C3D highmem

Machine types Max number of disks per VM,
across all disks*
Max total disk size (TB)
across all disks
Max number of
Hyperdisk
volumes
Local SSD
c3d-highmem-4 128 257 24 Not supported
c3d-highmem-8 128 257 32 Not supported
c3d-highmem-16 128 257 48 Not supported
c3d-highmem-30 128 257 64 Not supported
c3d-highmem-60 128 512 64 Not supported
c3d-highmem-90 128 512 64 Not supported
c3d-highmem-180 128 512 64 Not supported
c3d-highmem-360 128 512 64 Not supported

C3D with Local SSD

Machine types Max number of disks per VM,
across all disks*
Max total disk size (TB)
across all disks
Max number of
Hyperdisk
volumes
Local SSD partitions
(Total disk space)
c3d-standard-8-lssd 128 257 32 1 (375 GiB)
c3d-standard-16-lssd 128 257 32 1 (375 GiB)
c3d-standard-30-lssd 128 257 64 2 (750 GiB)
c3d-standard-60-lssd 128 512 64 4 (1.5 TiB)
c3d-standard-90-lssd 128 512 64 8 (3 TiB)
c3d-standard-180-lssd 128 512 64 16 (6 TiB)
c3d-standard-360-lssd 128 512 64 32 (12 TiB)

* The maximum size per Persistent Disk is 64 TiB. The maximum Hyperdisk Throughput size per volume is 32 TiB.
The maximum total disk size applies to all disk types, (Persistent Disk and Hyperdisk), attached to the VM. VMs with less than 32 vCPUs have a maximum of 257 Persistent Disk. VMs with 32 or more vCPUs cannot exceed 257 Persistent Disk, but can have a total disk capacity for Persistent Disk and Hyperdisk storage up to 512 TiB.

Network support for C3D VMs

C3D VMs require gVNIC network interfaces. C3D supports up to 100 Gbps network bandwidth for standard networking and up to 200 Gbps with per VM Tier_1 networking performance.

Before migrating to C3D or creating C3D VMs, make sure that the operating system image that you use is fully supported for C3D. Fully supported images include the updated gVNIC driver, even if the guest OS shows the gve driver version as 1.0.0. If your C3D VM is using an operating system with limited support, which includes an older version of the gVNIC driver, the VM might not be able to achieve the maximum network bandwidth for C3D VMs.

If you use a custom image with the C3D machine series, you can manually install the most recent gVNIC driver. The gVNIC driver version v1.3.0 or later is recommended for use with C3D VMs. Google recommends using the latest gVNIC driver version to benefit from additional features and bug fixes.

C3 machine series

C3 VMs are powered by the 4th generation Intel Xeon Scalable processors (code-named Sapphire Rapids), DDR5 memory, and Google's custom Intel Infrastructure Processing Engine (IPU). C3 machine types are optimized for the underlying NUMA architecture to deliver optimal, reliable, and consistent performance.

The new C3 machine series is a major leap in our purpose-built infrastructure offerings:

  • Leveraging our latest Infrastructure Processing Engine (IPU) to offload networking
  • Delivering high performance block-storage with Google Cloud Hyperdisk
  • Speeding up ML training and inference with Intel AMX

C3 is the first machine series to launch with Google's IPU. The IPU enables higher levels of networking performance, isolation and security. The C3 machine series supports a default network bandwidth of up to 100 Gbps and up to 200 Gbps with per VM Tier_1 networking performance. The Google IPU has been designed from the ground up to enable updates that don't impact running workloads.

The C3 machine series provides some of the largest general-purpose machine types with up to 176 vCPUs and 1.4 TB of memory.

In summary, the C3 machine series:

  • Is powered by Intel 4th Generation Xeon processors and Google's IPU.
  • Supports up to 176 vCPUs and 1.4 TB of DDR5 memory.
  • Supports standard network configuration with up to 100 Gbps bandwidth and Tier_1 networking with up to 200 Gbps bandwidth.
  • Supports Intel Advanced Matrix Extensions (AMX), a built-in accelerator that significantly improves the performance of deep-learning training and inference on the CPU.
  • Supports the following discount and consumption options:
  • Does not support sustained use discounts (SUDs).

C3 machine types

C3 VMs are available in the following instance configurations in six instance sizes ranging from 4 to 176 vCPUs and up to 1,408 GB of memory.

  • highcpu: 2 GB memory per vCPU
  • standard: 4 GB memory per vCPU
  • highmem: 8 GB memory per vCPU

To use Local SSD with C3, create your VM using the -lssd variant of the C3 machine types. Selecting this machine type creates a VM of the specified size with Local SSD partitions attached. You must use a c3-standard-*-lssd machine type to use Local SSD with your VM; you can't attach Local SSD volumes separately.

C3 standard

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3-standard-4 4 16 up to 23 N/A
c3-standard-8 8 32 up to 23 N/A
c3-standard-22 22 88 up to 23 N/A
c3-standard-44 44 176 up to 32 up to 50
c3-standard-88 88 352 up to 62 up to 100
c3-standard-176 176 704 up to 100 up to 200

* A vCPU represents a single hardware thread, or logical core.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3 highcpu

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3-highcpu-4 4 8 up to 23 N/A
c3-highcpu-8 8 16 up to 23 N/A
c3-highcpu-22 22 44 up to 23 N/A
c3-highcpu-44 44 88 up to 32 up to 50
c3-highcpu-88 88 176 up to 62 up to 100
c3-highcpu-176 176 352 up to 100 up to 200

* A vCPU represents a single hardware thread, or logical core.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3 highmem

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3-highmem-4 4 32 up to 23 N/A
c3-highmem-8 8 64 up to 23 N/A
c3-highmem-22 22 176 up to 23 N/A
c3-highmem-44 44 352 up to 32 up to 50
c3-highmem-88 88 704 up to 62 up to 100
c3-highmem-176 176 1408 up to 100 up to 200

* A vCPU represents a single hardware thread, or logical core.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3 with Local SSD

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier_1 egress bandwidth (Gbps)#
c3-standard-4-lssd 4 16 up to 23 N/A
c3-standard-8-lssd 8 32 up to 23 N/A
c3-standard-22-lssd 22 88 up to 23 N/A
c3-standard-44-lssd 44 176 up to 32 up to 50
c3-standard-88-lssd 88 352 up to 62 up to 100
c3-standard-176-lssd 176 704 up to 100 up to 200

* A vCPU represents a single hardware thread, or logical core.
Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
# Supports high-bandwidth networking for larger machine types.

C3 doesn't support custom machine types.

Supported disk types for C3

C3 VMs support only the NVMe disk interface and can use the following block storage types:

  • Zonal balanced Persistent Disk (pd-balanced)
  • Zonal SSD (performance) Persistent Disk (pd-ssd)
  • Hyperdisk Extreme (hyperdisk-extreme); Requires at least 64 vCPUs
  • Hyperdisk Throughput (hyperdisk-throughput)
  • Local SSD (only available with -lssd machine types)

A set amount of Local SSD disks are added to the C3 VM when you use the -lssd machine type. This is the only way to include Local SSD storage with a C3 VM.

Disk and capacity limits

You can use a mixture of Persistent Disk and Hyperdisk volumes with a VM, but the following restrictions apply.

  • The combined number of both Hyperdisk and Persistent Disk volumes can't exceed 128.
  • The total capacity of all Persistent Disk volumes can't exceed 257 TiB.
  • The number of Hyperdisk volumes of all types that you can attach to a VM can't exceed the limits stated in the Max number of Hyperdisk volumes column in the following table. For details about these limits, see Hyperdisk capacity.

Local SSD disks are not included in any of the aforementioned limits.

C3 standard

Machine types Max number of
disks per VM
across all disks*
Max total disk size (TiB)
across all disks
Max number of Hyperdisk
volumes
Local SSD
c3-standard-4 128 257 24 Not supported
c3-standard-8 128 257 32 Not supported
c3-standard-22 128 257 48 Not supported
c3-standard-44 128 512 64 Not supported
c3-standard-88 128 512 64 Not supported
c3-standard-176 128 512 64 Not supported

C3 highcpu

Machine types Max number of disks per VM
across all disks*
Max total disk size (TiB)
across all disks
Max number of Hyperdisk
volumes
Local SSD
c3-highcpu-4 128 257 24 Not supported
c3-highcpu-8 128 257 32 Not supported
c3-highcpu-22 128 257 48 Not supported
c3-highcpu-44 128 512 64 Not supported
c3-highcpu-88 128 512 64 Not supported
c3-highcpu-176 128 512 64 Not supported

C3 highmem

Machine types Max number of disks per VM,
across all disks*
Max total disk size (TiB)
across all disks
Max number of
Hyperdisk
volumes
Local SSD
c3-highmem-4 128 257 24 Not supported
c3-highmem-8 128 257 32 Not supported
c3-highmem-22 128 257 48 Not supported
c3-highmem-44 128 512 64 Not supported
c3-highmem-88 128 512 64 Not supported
c3-highmem-176 128 512 64 Not supported

C3 with Local SSD

Machine types Max number of disks per VM,
across all disks*
Max number of Hyperdisk
volumes
Max total disk size (TiB)
across all disks
Local SSD partitions (Total disk space)
c3-standard-4-lssd 128 24 257 1 (375 GiB)
c3-standard-8-lssd 128 32 257 2 (750 GiB)
c3-standard-22-lssd 128 48 257 4 (1.5 TiB)
c3-standard-44-lssd 128 64 512 8 (3 TiB)
c3-standard-88-lssd 128 64 512 16 (6 TiB)
c3-standard-176-lssd 128 64 512 32 (12 TiB)

*For Hyperdisk Throughput, the maximum size per volume is 32 TiB. For all other Persistent Disk or Hyperdisk volumes, the maximum size is 64 TiB.

Network support for C3 VMs

C3 VMs require gVNIC network interfaces. C3 supports up to 100 Gbps network bandwidth for standard networking and up to 200 Gbps with per VM Tier_1 networking performance.

Before migrating to C3 or creating C3 VMs, make sure that the operating system image that you use is fully supported for C3. Fully supported images include the updated gVNIC driver, even if the guest OS shows the gve driver version as 1.0.0. If your C3 VM is using an operating system with limited support, which includes an older version of the gVNIC driver, the VM might not be able to achieve the maximum network bandwidth for C3 VMs.

If you use a custom image with the C3 machine series, you can manually install the most recent gVNIC driver. The gVNIC driver version v1.3.0 or later is recommended for use with C3 VMs. Google recommends using the latest gVNIC driver version to benefit from additional features and bug fixes.

E2 machine series

The cost-optimized E2 machine series have between 2 to 32 vCPUs with a ratio of 0.5 GB to 8 GB of memory per vCPU for standard VMs, and 0.25 to 1 vCPUs with 0.5 GB to 8 GB of memory for shared-core E2 machine types. The E2 machine series offers both Intel and AMD EPYC processors. The processor is selected for you at the time of VM creation. Machine types in this series are available in all regions and zones and support a virtio memory balloon device.

In summary, the E2 machine series:

Shared-core VMs

The E2 machine series also contains shared-core machine types that use context- switching to time-share a physical core between vCPUs for multitasking. Different shared-core machine types sustain different amounts of time on a physical core.

Unlike predefined machine types and custom machine types, shared-core machine types have a predefined price that includes both vCPUs and memory. For more information, see VM instance pricing.

CPU bursting

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

  • e2-micro, e2-small, and e2-medium shared-core VMs can burst for dozens of seconds.
  • If the CPU is utilized at 100%, then the burst lasts as follows:
    • e2-micro: 30 seconds
    • e2-small: 60 seconds
    • e2-medium 120 seconds
The exact burst time is determined by a Token bucket meaning utilizing the CPU less than 100% will result in longer bursts. Bursting doesn't incur any additional charges. You are charged the listed on-demand price for e2 shared-core, f1-micro, and g1-small VMs.

E2 Limitations

  • The E2 machine series does not offer SUDs; however, it provides consistently low on-demand and committed-use pricing.
  • The E2 machine series does not support GPUs, Local SSDs, sole-tenant nodes, or nested virtualization.

E2 machine types

E2 is available in standard, highmem, and highcpu configurations, as well as shared-core machine type. In general, E2 shared-core machine types can be more cost-effective for running small, non-resource intensive applications than standard, high-memory, or high-CPU machine types.

E2 standard

E2 standard machine types have 4 GB of system memory per vCPU.

Machine types vCPUs Memory (GB) Max number of persistent disks (PDs) Max total PD size (TiB) Local SSD Maximum egress bandwidth (Gbps)
e2-standard-2 2 8 128 257 No 4
e2-standard-4 4 16 128 257 No 8
e2-standard-8 8 32 128 257 No 16
e2-standard-16 16 64 128 257 No 16
e2-standard-32 32 128 128 257 No 16
Persistent Disk and Hyperdisk usage is charged separately from machine pricing.
Maximum egress bandwidth cannot exceed the number given. Actual See Network bandwidth.

E2 high-mem

E2 high-memory machine types have 8 GB of system memory per vCPU.

Machine types vCPUs Memory (GB) Max number of persistent disks (PDs) Max total PD size (TiB) Local SSD Maximum egress bandwidth (Gbps)
e2-highmem-2 2 16 128 257 No 4
e2-highmem-4 4 32 128 257 No 8
e2-highmem-8 8 64 128 257 No 16
e2-highmem-16 16 128 128 257 No 16
Persistent Disk and Hyperdisk usage is charged separately from machine pricing.
Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.

E2 high-cpu

E2 high-cpu machine types have 1 GB of system memory per vCPU.

Machine types vCPUs Memory (GB) Max number of persistent disks (PDs) Max total PD size (TiB) Local SSD Maximum egress bandwidth (Gbps)
e2-highcpu-2 2 2 128 257 No 4
e2-highcpu-4 4 4 128 257 No 8
e2-highcpu-8 8 8 128 257 No 16
e2-highcpu-16 16 16 128 257 No 16
e2-highcpu-32 32 32 128 257 No 16
Persistent Disk and Hyperdisk usage is charged separately from machine pricing.
Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.

E2 shared-core

E2 shared-core machine types are cost-effective, have a virtio memory balloon device, and are ideal for small workloads. When you use E2 shared-core machine types, your VM runs two vCPUs simultaneously shared on one physical core for a specific fraction of time depending on the machine type. Each vCPU can burst up to 100% of CPU time, for short periods, before returning to the time limitations described in the preceding section.

  • e2-micro sustains 2 vCPUs, each for 12.5% of CPU time totaling 25% CPU time.
  • e2-small sustains 2 vCPUs, each at 25% of CPU time totaling 50% CPU time.
  • e2-medium sustains 2 vCPUs, each at 50% of CPU time totaling 100% CPU time.

Machine types Description vCPUs Fractional vCPUs* Memory (GB) Max number of persistent disks (PDs) Max total PD size (TiB) Local SSD Maximum egress bandwidth (Gbps)
e2-micro Micro machine type with 0.25 vCPU and 1 GB of memory, backed by a shared physical core. 2 0.25* 1 16 3 no 1
e2-small Small machine type with 0.5 vCPU and 2 GB of memory, backed by a shared physical core. 2 0.5* 2 16 3 no 1
e2-medium Medium machine type with 1 vCPU and 4 GB of memory, backed by a shared physical core. 2 1* 4 16 3 no 2
* Fractional vCPU of 0.25, 0.5, or 1.0 with 2 vCPUs exposed to the guest operating system.
Persistent Disk and Hyperdisk usage is charged separately from machine pricing.
Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.

Supported disk types for E2 VMs

E2 VMs can use the following block storage types:

  • Zonal and regional balanced Persistent Disk (pd-balanced)
  • Zonal and regional SSD Persistent Disk (pd-ssd)
  • Zonal and regional standard Persistent Disk (pd-standard)

N2 machine series

The N2 machine series has flexible sizing between 2 to 128 vCPUs and 0.5 to 8 GB of memory per vCPU. Machine types in this series run on the following processors:

  • Ice Lake—offered in specific regions and zones. It is the default processor for larger machine types.

  • Cascade Lake—the default for machine types up to 80 vCPUs. If you want to create VMs with Ice Lake, you must set it as the minimum CPU platform.

You can find more details about these two processors on the CPU platforms page.

Workloads that can take advantage of the higher clock frequency are a good choice for this series. These workloads can get higher per-thread performance while benefiting from all the flexibility that the general-purpose machine family offers.

In summary, the N2 machine series:

N2 machine types

N2 standard

N2 standard machine types have 4 GB of system memory per vCPU.

Machine types vCPUs* Memory (GB) Default egress bandwidth (Gbps) Tier 1 egress bandwidth (Gbps)#
n2-standard-2 2 8 10 N/A
n2-standard-4 4 16 10 N/A
n2-standard-8 8 32 16 N/A
n2-standard-16 16 64 32 N/A
n2-standard-32 32 128 32 50
n2-standard-48 48 192 32 50
n2-standard-64 64 256 32 75
n2-standard-80 80 320 32 100
n2-standard-96 96 384 32 100
n2-standard-128 128 512 32 100

* A vCPU is implemented as a single hardware thread, or logical core, on one of the available CPU platforms.
Max