General-purpose machine family for Compute Engine

This document describes the features of the Compute Engine general-purpose machine family, which 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.

C4D is powered by the fifth generation AMD EPYC Turin processor and Titanium. These machine types have up to 384 vCPUs and 3,024 GB of DDR5 memory, a max-boost frequency of 4.1 GHz, and up to 200 Gbps per VM Tier_1 networking performance. C4D also offers Local SSD (-lssd) machine types and bare metal (-metal) machine types.

C4A is powered by Google's Axion processor built on the Arm Neoverse V2 compute core. C4A provides standard, highcpu, and highmem machine types with up to 72 vCPUs, 576 GB DDR5 memory, 6 TiB of local Titanium SSD, and up to 100 Gbps with per VM Tier_1 networking performance. C4A also offers Local SSD (-lssd) machine types and a highmem bare metal (-metal) machine type with 96 vCPUs and 768 GB DDR5 memory.

C4 is powered by the sixth generation (code-named Granite Rapids) and fifth generation (code-named Emerald Rapids) Intel Xeon Scalable processors. C4 instances running on Granite Rapids offer a sustained, all-core turbo frequency of 3.9 GHz and a max turbo frequency of 4.2 GHz, 2.2 TB of DDR5 memory, 18 TiB of Titanium SSD for C4. supports up to 200 Gbps of per VM Tier_1 networking performance. C4 also offers Local SSD (-lssd) machine types and bare metal (-metal) machine types.

N4D is powered by the fifth generation AMD EPYC Turin processor and Titanium. These machine types have up to 96 vCPUs and 768 GB of DDR5 memory, and a max-boost frequency of 4.1 GHz. N4D offers 50 Gbps of standard network bandwidth.

N4A is powered by Google's Axion processor built on the Arm Neoverse N3 compute core. N4A provides machine types of up to 64 vCPUs and 512 GB of DDR5 memory. N4A is available in standard, high-mem, high-cpu, and custom machine types with extended memory, and up to 50 Gbps of standard networking.

N4 is powered by the fifth generation Intel Xeon Scalable processor (code-named Emerald Rapids). N4 offers a sustained, all-core turbo frequency of 2.9 GHz, 640 GB of DDR5 memory, and up to 50 Gbps of standard network bandwidth.

C3 is powered by fourth 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.

C3D is powered by fourth generation AMD EPYC Genoa processors and offers a sustained, all-core turbo frequency of 3.3 GHz, 2,880 GB of DDR5 memory, and up to 200 Gbps per VM Tier_1 networking performance.

For bare metal machine types, choose the C4, C4D, or C3 machine series.

All third and fourth generation general-purpose VMs support Titanium.

E2, E2 shared-core, N2, N2D, Tau T2A, and Tau T2D are second generation machine series in this family; N1 and its related shared-core machine types are the first generation machine series.

Machine series Workloads
N4, N4A, N4D, N2, N2D, N1
  • Medium traffic web and application servers
  • Containerized microservices
  • Business intelligence applications
  • Virtual desktops
  • CRM applications
  • Development and test environments
  • Batch processing
  • Storage and archive
C4A, C4, C4D, 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
Tau T2A, Tau T2D
  • Scale-out workloads
  • Web servers
  • Containerized microservices
  • Media transcoding
  • Large-scale Java applications

C4D machine series

C4D VMs are powered by the fifth generation AMD EPYC Turin processor and Titanium. C4D delivers a 30% performance boost over C3D on the estimated SPECrate®2017_int_base benchmark, which lets you scale performance with fewer resources, thereby optimizing your costs.

C4D is designed to run workloads including web, app and game servers, AI inference, video streaming, and data centric applications like analytics, as well as relational and in-memory databases.

For databases, C4D delivers 55% more queries per second for MySQL and 35% higher operations per second for Memorystore for Redis workloads compared to C3D due to its higher core frequency (up to 4.1 GHz) and improved Instructions Per Clock (IPC).

For web-serving workloads, AMD EPYC Turin's advancements in L3-cache efficiency and branch prediction enable up to 80% higher throughput per vCPU with C4D.

In summary, the C4D machine series has the following features:

  • Powered by the AMD EPYC Turin CPU and Titanium.
  • Supports up to 384 vCPUs and 3,024 GB of DDR5 memory.
  • Supports up to 12 TiB of local Titanium SSD disks.
  • Offers predefined machine types that range in size from 2 to 384 vCPUs.
  • Supports up to 3,024 GB of DDR5 memory for VM instances and up to 3,072 GB of memory for bare metal instances.
  • Supports consumption options like on-demand, Spot VMs, and future reservations.
  • Supports standard network configuration with up to 100 Gbps bandwidth.
  • Supports per VM Tier_1 networking performance with up to 200 Gbps bandwidth.
  • Supports only Hyperdisk volumes.
  • Supports Confidential VM with AMD SEV, excluding bare metal instances and configurations with more than 255 vCPUs.
  • Supports resource-based and flexible committed use discounts (CUDs).
  • Supports compact and spread placement policies.

C4D machine types

C4D VMs are available as predefined configurations in standard, highcpu, and highmem sizes ranging from 2 vCPU to 384 vCPUs and up to 3,024 GB of memory.

To use Titanium SSD with C4D, create your instance using the -lssd variant of the C4D machine types. Selecting this machine type creates an instance of the specified size with Titanium SSD partitions attached. You can't attach Titanium SSD volumes separately.

To create a bare metal instance with C4D, use one of the following machine types:

  • c4d-standard-384-metal
  • c4d-highcpu-384-metal
  • c4d-highmem-384-metal

C4D standard

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains5 Default egress bandwidth (Gbps)3 Tier_1 egress bandwidth (Gbps)4
c4d-standard-2 2 7 No 1 shared Up to 10 N/A
c4d-standard-4 4 15 No 1 shared Up to 20 N/A
c4d-standard-8 8 31 No 1 shared Up to 20 N/A
c4d-standard-16 16 62 No 1 shared Up to 20 N/A
c4d-standard-32 32 124 No 1 shared Up to 23 N/A
c4d-standard-48 48 186 No 1 shared Up to 34 Up to 50
c4d-standard-64 64 248 No 1 shared Up to 45 Up to 75
c4d-standard-96 96 372 No 1 shared Up to 67 Up to 100
c4d-standard-192 192 744 No 1 isolated Up to 100 Up to 150
c4d-standard-384 384 1,488 No 2 (full machine) Up to 100 Up to 200
c4d-standard-384-metal2 384 1,536 No 2 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 For bare metal instances, the number of vCPUs is equivalent to the number of hardware threads on the host server.
3 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
4 Supports high-bandwidth networking for larger machine types.
5 The number of vNUMA nodes exposed to the guest OS.

C4D highcpu

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains5 Default egress bandwidth (Gbps)3 Tier_1 egress bandwidth (Gbps)4
c4d-highcpu-2 2 3 No 1 shared Up to 10 N/A
c4d-highcpu-4 4 7 No 1 shared Up to 20 N/A
c4d-highcpu-8 8 15 No 1 shared Up to 20 N/A
c4d-highcpu-16 16 30 No 1 shared Up to 20 N/A
c4d-highcpu-32 32 60 No 1 shared Up to 23 N/A
c4d-highcpu-48 48 90 No 1 shared Up to 34 Up to 50
c4d-highcpu-64 64 120 No 1 shared Up to 45 Up to 75
c4d-highcpu-96 96 180 No 1 shared Up to 67 Up to 100
c4d-highcpu-192 192 360 No 1 isolated Up to 100 Up to 150
c4d-highcpu-384 384 720 No 2 (full machine) Up to 100 Up to 200
c4d-highcpu-384-metal2 384 768 No 2 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 For bare metal instances, the number of vCPUs is equivalent to the number of hardware threads on the host server.
3 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
4 Supports high-bandwidth networking for larger machine types.
5 The number of vNUMA nodes exposed to the guest OS.

C4D highmem

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains5 Default egress bandwidth (Gbps)3 Tier_1 egress bandwidth (Gbps)4
c4d-highmem-2 2 15 No 1 shared Up to 10 N/A
c4d-highmem-4 4 31 No 1 shared Up to 20 N/A
c4d-highmem-8 8 63 No 1 shared Up to 20 N/A
c4d-highmem-16 16 126 No 1 shared Up to 20 N/A
c4d-highmem-32 32 252 No 1 shared Up to 23 N/A
c4d-highmem-48 48 378 No 1 shared Up to 34 Up to 50
c4d-highmem-64 64 504 No 1 shared Up to 45 Up to 75
c4d-highmem-96 96 756 No 1 shared Up to 67 Up to 100
c4d-highmem-192 192 1,512 No 1 isolated Up to 100 Up to 150
c4d-highmem-384 384 3,024 No 2 (full machine) Up to 100 Up to 200
c4d-highmem-384-metal2 384 3,072 No 2 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 For bare metal instances, the number of vCPUs is equivalent to the number of hardware threads on the host server.
3 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
4 Supports high-bandwidth networking for larger machine types.
5 The number of vNUMA nodes exposed to the guest OS.

C4D standard

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains5 Default egress bandwidth (Gbps)3 Tier_1 egress bandwidth (Gbps)4
c4d-standard-8-lssd 8 31 (1 x 375 GiB) 375 GiB 1 shared Up to 20 N/A
c4d-standard-16-lssd 16 62 (1 x 375 GiB) 375 GiB 1 shared Up to 20 N/A
c4d-standard-32-lssd 32 124 (2 x 375 GiB) 750 GiB 1 shared Up to 23 N/A
c4d-standard-48-lssd 48 186 (4 x 375 GiB) 1,500 GiB 1 shared Up to 34 Up to 50
c4d-standard-64-lssd 64 248 (6 x 375 GiB) 2,250 GiB 1 shared Up to 45 Up to 75
c4d-standard-96-lssd 96 372 (8 x 375 GiB) 3,000 GiB 1 shared Up to 67 Up to 100
c4d-standard-192-lssd 192 744 (16 x 375 GiB) 6,000 GiB 1 isolated Up to 100 Up to 150
c4d-standard-384-lssd 384 1,488 (32 x 375 GiB) 12,000 GiB 2 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 For bare metal instances, the number of vCPUs is equivalent to the number of hardware threads on the host server.
3 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
4 Supports high-bandwidth networking for larger machine types.
5 The number of vNUMA nodes exposed to the guest OS.

C4D highmem

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains5 Default egress bandwidth (Gbps)3 Tier_1 egress bandwidth (Gbps)4
c4d-highmem-8-lssd 8 63 (1 x 375 GiB) 375 GiB 1 shared Up to 20 N/A
c4d-highmem-16-lssd 16 126 (1 x 375 GiB) 375 GiB 1 shared Up to 20 N/A
c4d-highmem-32-lssd 32 252 (2 x 375 GiB) 750 GiB 1 shared Up to 23 N/A
c4d-highmem-48-lssd 48 378 (4 x 375 GiB) 1,500 GiB 1 shared Up to 34 Up to 50
c4d-highmem-64-lssd 64 504 (6 x 375 GiB) 2,250 GiB 1 shared Up to 45 Up to 75
c4d-highmem-96-lssd 96 756 (8 x 375 GiB) 3,000 GiB 1 shared Up to 67 Up to 100
c4d-highmem-192-lssd 192 1,512 (16 x 375 GiB) 6,000 GiB 1 isolated Up to 100 Up to 150
c4d-highmem-384-lssd 384 3,024 (32 x 375 GiB) 12,000 GiB 2 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 For bare metal instances, the number of vCPUs is equivalent to the number of hardware threads on the host server.
3 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
4 Supports high-bandwidth networking for larger machine types.
5 The number of vNUMA nodes exposed to the guest OS.

C4D doesn't support custom machine types.

Regional availability for C4D instances

For C4D VMs, you can view the available regions and zones in the Available regions and zones table, as follows:

  • To view all the zones where you can create a C4D VM, in the Select a machine series menu, select C4D.
  • You can also use the Select a location menu to limit the results to a geographical area.

For regional availability of C4D bare metal instances, see Bare metal instances on Compute Engine.

Supported disk types for C4D

C4D VMs support only the NVMe disk interface and can use the following Hyperdisk block storage:

  • Hyperdisk Balanced (hyperdisk-balanced)
  • Hyperdisk Extreme (hyperdisk-extreme)
  • Hyperdisk Throughput (hyperdisk-throughput)
  • Local Titanium SSD (added automatically with -lssd machine types)

C4D doesn't support Persistent Disk.

Disk and capacity limits

You can attach a mixture of different Hyperdisk types to an instance, but 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

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

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

C4D storage limits are described in the following table:

C4D standard

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Throughput Hyperdisk ML Hyperdisk Extreme
c4d-standard-2 4 4 4 0 0
c4d-standard-4 8 8 8 0 0
c4d-standard-8 16 16 16 0 0
c4d-standard-16 32 32 32 0 0
c4d-standard-32 32 32 32 0 0
c4d-standard-48 32 32 32 0 0
c4d-standard-64 32 32 64 0 8
c4d-standard-96 32 32 64 0 8
c4d-standard-192 64 64 64 0 8
c4d-standard-384 128 128 128 0 8
c4d-standard-384-metal 128 128 8 0 8

C4D highcpu

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Throughput Hyperdisk ML Hyperdisk Extreme
c4d-highcpu-2 4 4 4 0 0
c4d-highcpu-4 8 8 8 0 0
c4d-highcpu-8 16 16 16 0 0
c4d-highcpu-16 32 32 32 0 0
c4d-highcpu-32 32 32 32 0 0
c4d-highcpu-48 32 32 32 0 0
c4d-highcpu-64 32 32 64 0 8
c4d-highcpu-96 32 32 64 0 8
c4d-highcpu-192 64 64 64 0 8
c4d-highcpu-384 128 128 128 0 8
c4d-highcpu-384-metal 128 128 8 0 8

C4D highmem

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Throughput Hyperdisk ML Hyperdisk Extreme
c4d-highmem-2 4 4 4 0 0
c4d-highmem-4 8 8 8 0 0
c4d-highmem-8 16 16 16 0 0
c4d-highmem-16 32 32 32 0 0
c4d-highmem-32 32 32 32 0 0
c4d-highmem-48 32 32 64 0 0
c4d-highmem-64 32 32 64 0 8
c4d-highmem-96 32 32 64 0 8
c4d-highmem-192 64 64 64 0 8
c4d-highmem-384 128 128 128 0 8
c4d-highmem-384-metal 128 128 8 0 8

C4D standard

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Throughput Hyperdisk ML Hyperdisk Extreme
c4d-standard-8-lssd 16 16 16 0 0
c4d-standard-16-lssd 32 32 32 0 0
c4d-standard-32-lssd 32 32 32 0 0
c4d-standard-48-lssd 32 32 32 0 0
c4d-standard-64-lssd 32 32 64 0 8
c4d-standard-96-lssd 32 32 64 0 8
c4d-standard-192-lssd 64 64 64 0 8
c4d-standard-384-lssd 128 128 128 0 8

C4D highmem

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Throughput Hyperdisk ML Hyperdisk Extreme
c4d-highmem-8-lssd 16 16 16 0 0
c4d-highmem-16-lssd 32 32 32 0 0
c4d-highmem-32-lssd 32 32 32 0 0
c4d-highmem-48-lssd 32 32 32 0 0
c4d-highmem-64-lssd 32 32 64 0 8
c4d-highmem-96-lssd 32 32 64 0 8
c4d-highmem-192-lssd 64 64 64 0 8
c4d-highmem-384-lssd 128 128 128 0 8

Network support for C4D instances

The following network interface drivers are required:

C4D supports up to 100 Gbps network bandwidth for standard networking and up to 200 Gbps with per VM Tier_1 networking performance for VM and bare metal instances.

Before migrating to C4D or creating C4D VMs or bare metal instances, make sure that the operating system image that you use supports the IDPF network driver for bare metal instances or the gVNIC driver for VM instances. To get the best possible performance on C4D VMs, choose an OS image that supports both "Tier_1 Networking" and "200 Gbps network bandwidth". These images include an updated gVNIC driver, even if the guest OS shows the gve driver version as 1.0.0. If your C4D VM is using an operating system with an older version of gVNIC driver, this is still supported but the VM might experience suboptimal performance such as less network bandwidth or higher latency.

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

Maintenance experience for C4D instances

During the lifespan of a virtual machine (VM) instance, the host machine that your instance runs undergoes multiple host events. A host event can include the regular maintenance of Compute Engine infrastructure, or in rare cases, a host error. Compute Engine also applies some non-disruptive lightweight upgrades for the hypervisor and network in the background.

The C4D machine series offers the following features related to host maintenance:

Machine type Typical scheduled maintenance event frequency Maintenance behavior Advanced notification On-demand maintenance Simulate maintenance
c4d-*-lssd Minimum of 30 days Live migrate 7 days Yes Yes
c4d-*-384 Minimum of 30 days Live migrate 7 days Yes Yes
All others Minimum of 30 days Live migrate 7 days No Yes

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

C4A machine series

C4A VMs are powered by Google's first Arm Axion™ processor. C4A provides machine types with up to 72 vCPUs and 576 GB of DDR5 memory, and 6 TiB of local Titanium SSD. C4A is available in standard, highmem, and highcpu machine types. It also offers -lssd variants for Titanium SSD and a highmem bare metal machine type with 96 vCPUs and 768 GB of DDR5 memory. C4A uses Google Cloud's latest generation of Google Cloud Hyperdisk storage options and Titanium SSD. C4A offers up to 50 Gbps of standard network performance, and up to 100 Gbps per VM Tier_1 networking performance for your instances.

C4A VMs are placed within a single node with Uniform Memory Access (UMA) and also support sole tenant nodes to deliver consistent performance.

In summary, the C4A machine series has the following features:

  • Is powered by the Google Axion CPU and Titanium.
  • Supports multiple predefined machine types with up to 72 vCPUs and 576 GB of DDR5 memory.
  • Supports up to 6 TiB of local Titanium SSD disks.
  • Supports highmem bare metal instances with 96 vCPUs and 768 GB of DDR5 memory.
  • Supports standard network configuration with up to 50 Gbps bandwidth.
  • Supports per VM Tier_1 networking performance with up to 100 Gbps bandwidth.
  • Supports Hyperdisk only.
  • Supports the following discount and consumption options:
  • Supports the performance monitoring unit (PMU).
  • Doesn't support compact placement policies.
  • Doesn't support suspend with C4A instances that have attached Titanium SSD disks.

For information about migrating to Arm VMs, read the Arm on Compute document.

C4A machine types

C4A VMs are available as predefined configurations in sizes ranging from 1 vCPU to 72 vCPUs and up to 576 GB of memory.

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

To use Titanium SSD with C4A, create your VM using the -lssd variant of the C4A machine types. Selecting this machine type creates a VM of the specified size with Titanium SSD partitions attached. You can't attach Titanium SSD volumes separately.

You can create a bare metal instance with a c4a-highmem-96-metal machine type.

C4A standard

Machine types vCPUs1 Memory (GB) Titanium SSD Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4a-standard-1 1 4 No Up to 10 N/A
c4a-standard-2 2 8 No Up to 10 N/A
c4a-standard-4 4 16 No Up to 23 N/A
c4a-standard-8 8 32 No Up to 23 N/A
c4a-standard-16 16 64 No Up to 23 N/A
c4a-standard-32 32 128 No Up to 23 Up to 50
c4a-standard-48 48 192 No Up to 34 Up to 50
c4a-standard-64 64 256 No Up to 45 Up to 75
c4a-standard-72 72 288 No Up to 50 Up to 100

1 SMT is not supported. Each vCPU is equivalent to an entire core. See CPU platforms.
2 Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.

C4A highcpu

Machine types vCPUs1 Memory (GB) Titanium SSD Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4a-highcpu-1 1 2 No Up to 10 N/A
c4a-highcpu-2 2 4 No Up to 10 N/A
c4a-highcpu-4 4 8 No Up to 23 N/A
c4a-highcpu-8 8 16 No Up to 23 N/A
c4a-highcpu-16 16 32 No Up to 23 N/A
c4a-highcpu-32 32 64 No Up to 23 Up to 50
c4a-highcpu-48 48 96 No Up to 34 Up to 50
c4a-highcpu-64 64 128 No Up to 45 Up to 75
c4a-highcpu-72 72 144 No Up to 50 Up to 100

1 SMT is not supported. Each vCPU is equivalent to an entire core. See CPU platforms.
2 Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.

C4A highmem

Machine types vCPUs1 Memory (GB) Titanium SSD Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4a-highmem-1 1 8 No Up to 10 N/A
c4a-highmem-2 2 16 No Up to 10 N/A
c4a-highmem-4 4 32 No Up to 23 N/A
c4a-highmem-8 8 64 No Up to 23 N/A
c4a-highmem-16 16 128 No Up to 23 N/A
c4a-highmem-32 32 256 No Up to 23 Up to 50
c4a-highmem-48 48 384 No Up to 34 Up to 50
c4a-highmem-64 64 512 No Up to 45 Up to 75
c4a-highmem-72 72 576 No Up to 50 Up to 100
c4a-highmem-96-metal 96 768 No Up to 50 Up to 100

1 SMT is not supported. Each vCPU is equivalent to an entire core. See CPU platforms.
2 Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.

C4A standard

Machine types vCPUs1 Memory (GB) Titanium SSD Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4a-standard-4-lssd 4 16 (1 x 375 GiB) 375 GiB Up to 23 N/A
c4a-standard-8-lssd 8 32 (2 x 375 GiB) 750 GiB Up to 23 N/A
c4a-standard-16-lssd 16 64 (4 x 375 GiB) 1,500 GiB Up to 23 N/A
c4a-standard-32-lssd 32 128 (6 x 375 GiB) 2,250 GiB Up to 23 Up to 50
c4a-standard-48-lssd 48 192 (10 x 375 GiB) 3,750 GiB Up to 34 Up to 50
c4a-standard-64-lssd 64 256 (14 x 375 GiB) 5,250 GiB Up to 45 Up to 75
c4a-standard-72-lssd 72 288 (16 x 375 GiB) 6,000 GiB Up to 50 Up to 100

1 SMT is not supported. Each vCPU is equivalent to an entire core. See CPU platforms.
2 Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.

C4A highmem

Machine types vCPUs* Memory (GB) Titanium SSD Default egress bandwidth (Gbps)‡ Tier_1 egress bandwidth (Gbps)#
c4a-highmem-4-lssd 4 32 (1 x 375 GiB) 375 GiB Up to 23 N/A
c4a-highmem-8-lssd 8 64 (2 x 375 GiB) 750 GiB Up to 23 N/A
c4a-highmem-16-lssd 16 128 (4 x 375 GiB) 1,500 GiB Up to 23 N/A
c4a-highmem-32-lssd 32 256 (6 x 375 GiB) 2,250 GiB Up to 23 Up to 50
c4a-highmem-48-lssd 48 384 (10 x 375 GiB) 3,750 GiB Up to 34 Up to 50
c4a-highmem-64-lssd 64 512 (14 x 375 GiB) 5,250 GiB Up to 45 Up to 75
c4a-highmem-72-lssd 72 576 (16 x 375 GiB) 6,000 GiB Up to 50 Up to 100

1 SMT is not supported. Each vCPU is equivalent to an entire core. See CPU platforms.
2 Maximum egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.

C4A doesn't support custom machine types.

Supported disk types for C4A

C4A VMs support only the NVMe disk interface and can use the following Hyperdisk block storage:

VM instances

  • Hyperdisk Balanced (hyperdisk-balanced)
  • Hyperdisk Balanced High Availability (hyperdisk-balanced-high-availability)
  • Hyperdisk Throughput (hyperdisk-throughput)
  • Hyperdisk Extreme (hyperdisk-extreme)
  • Hyperdisk ML (hyperdisk-ML)
  • Local Titanium SSD (only available with -lssd machine types)

Bare metal instances

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

C4A doesn't support Persistent Disk.

Disk and capacity limits

You can attach a mixture of different Hyperdisk types to an instance, but 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

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

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

C4A standard

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Balanced High Availability Hyperdisk Throughput Hyperdisk Extreme Hyperdisk ML
c4a-standard-1 16 16 16 16 0 16
c4a-standard-2 16 16 16 16 0 16
c4a-standard-4 16 16 16 16 0 16
c4a-standard-8 16 16 16 16 0 16
c4a-standard-16 32 32 32 32 0 32
c4a-standard-32 32 32 32 32 0 32
c4a-standard-48 32 32 32 32 0 32
c4a-standard-64 64 64 64 64 8 64
c4a-standard-72 64 64 64 64 8 64

C4A highcpu

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Balanced High Availability Hyperdisk Throughput Hyperdisk Extreme Hyperdisk ML
c4a-highcpu-1 16 16 16 16 0 16
c4a-highcpu-2 16 16 16 16 0 16
c4a-highcpu-4 16 16 16 16 0 16
c4a-highcpu-8 16 16 16 16 0 16
c4a-highcpu-16 32 32 32 32 0 32
c4a-highcpu-32 32 32 32 32 0 32
c4a-highcpu-48 32 32 32 32 0 32
c4a-highcpu-64 64 64 64 64 8 64
c4a-highcpu-72 64 64 64 64 8 64

C4A highmem

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Balanced High Availability Hyperdisk Throughput Hyperdisk Extreme Hyperdisk ML
c4a-highmem-1 16 8 16 16 0 16
c4a-highmem-2 16 8 16 16 0 16
c4a-highmem-4 16 16 16 16 0 16
c4a-highmem-8 16 16 16 16 0 16
c4a-highmem-16 32 32 32 32 0 32
c4a-highmem-32 32 32 32 32 0 32
c4a-highmem-48 32 32 32 32 0 32
c4a-highmem-64 64 64 64 64 8 64
c4a-highmem-72 64 64 64 64 8 64
c4a-highmem-96-metal 128 128 Not supported Not supported 8 32

C4A standard

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Balanced High Availability Hyperdisk Throughput Hyperdisk Extreme Hyperdisk ML
c4a-standard-4-lssd 16 16 16 16 0 16
c4a-standard-8-lssd 16 16 16 16 0 16
c4a-standard-16-lssd 32 32 32 32 0 32
c4a-standard-32-lssd 32 32 32 32 0 32
c4a-standard-48-lssd 32 32 32 32 0 32
c4a-standard-64-lssd 64 64 64 64 8 64
c4a-standard-72-lssd 64 64 64 64 8 64

C4A highmem

Maximum number of disks
Machine types Hyperdisk
per VM
Hyperdisk Balanced Hyperdisk Balanced High Availability Hyperdisk Throughput Hyperdisk Extreme Hyperdisk ML
c4a-highmem-4-lssd 16 16 16 16 0 16
c4a-highmem-8-lssd 16 16 16 16 0 16
c4a-highmem-16-lssd 32 32 32 32 0 32
c4a-highmem-32-lssd 32 32 32 32 0 32
c4a-highmem-48-lssd 32 32 32 32 0 32
c4a-highmem-64-lssd 64 64 64 64 8 64
c4a-highmem-72-lssd 64 64 64 64 8 64

Network support for C4A instances

The following network interface drivers are required:

C4A supports up to 100 Gbps network bandwidth for standard networking and bare metal instances.

Before migrating to C4A or creating C4A VMs or bare metal instances, make sure that the operating system image that you use supports the IDPF network driver for bare metal instances or the gVNIC driver for VM instances. To get the best possible performance on C4A VMs, choose an OS image that supports both "Tier_1 Networking" and "100 Gbps network bandwidth". These images include an updated gVNIC driver, even if the guest OS shows the gve driver version as 1.0.0. If your C4A VM is using an operating system with an older version of gVNIC driver, this is still supported but the VM might experience suboptimal performance such as less network bandwidth or higher latency.

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

Maintenance experience for C4A instances

During the lifespan of a virtual machine (VM) instance, the host machine that your instance runs undergoes multiple host events. A host event can include the regular maintenance of Compute Engine infrastructure, or in rare cases, a host error. Compute Engine also applies some non-disruptive lightweight upgrades for the hypervisor and network in the background.

The C4A machine series offers the following features related to host maintenance:

Machine type Typical scheduled maintenance event frequency Maintenance behavior Advanced notification On-demand maintenance
c4a-*-lssd Minimum of 30 days Live migrate 7 days Yes
c4a-*-metal Minimum of 30 days Terminate 7 days Yes
All others Minimum of 30 days Live migrate 7 days No

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

C4 machine series

C4 VMs are powered by 6th generation (code-named Granite Rapids) or 5th generation (code-named Emerald Rapids) Intel Xeon Scalable processors and Titanium. C4 Local SSD (-lssd) and bare metal (-metal) instances, as well as instances with 144 or 288 vCPUs, use the 6th generation Intel Granite Rapids processor. All other instances use the 5th generation Intel Emerald Rapids processor.

The C4 machine series is designed to deliver price-performance and enterprise-grade reliability along with a maintenance experience for your most demanding workloads. C4 instances are ideal for web and app serving, game servers, databases and caches, video streaming, data analytics, network appliances, and CPU-based ML inference.

C4 VMs are designed to achieve maximum performance from single-core turbo boosting. For more consistent vCPU performance, disable vCPU boosting and limit the vCPUs to the sustainable all-core turbo frequency. You can do this by setting turboMode=ALL_CORE_MAX in the AdvancedMachineFeatures settings.

In summary, the C4 machine series:

  • Is powered by the 6th generation Intel Granite Rapids or 5th generation Intel Emerald Rapids processor and Titanium IPU.
  • Lets you switch between core-boosting performance and steady all-core turbo performance for your vCPUs.
  • Supports up to 288 vCPUs and 2.2 TB of DDR5 memory.
  • Supports up to 18 TiB of local Titanium SSD disks.
  • Supports compact and spread placement policies.
  • Offers multiple predefined machine types.
  • Supports standard network configuration with up to 100 Gbps bandwidth.
  • Supports per VM Tier_1 networking performance 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:
  • Supports the performance monitoring unit (PMU).
  • Supports up to 192 vCPUs for Confidential VM with Intel TDX using Granite Rapids processors. Intel TDX support isn't available on Emerald Rapids processors.

C4 Limitations

  • You can't dynamically add or remove a disk when using Windows Server 25.
  • You can't dynamically add or remove multiple disks when using Windows Server 25 or Windows 11.
  • C4 VM shapes powered by Granite Rapids might experience lower networking performance on Windows 11 and Debian 11 OS images.

C4 machine types

C4 VMs are available as predefined configurations in sizes ranging from 2 vCPUs to 288 vCPUs and up to 2,232 GB of memory.

  • standard: 3.75 GB memory per vCPU
  • highcpu: 2 GB memory per vCPU
  • highmem: 7.75 GB memory per vCPU

To use Titanium SSD with C4, create your instance using the -lssd variant of the C4 machine types. Selecting this machine type creates an instance of the specified size with Titanium SSD partitions attached. You can't attach Titanium SSD volumes separately.

To create a bare metal instance with C4, use one of the following machine types:

  • c4-standard-288-metal
  • c4-standard-288-lssd-metal
  • c4-highmem-288-metal
  • c4-highmem-288-lssd-metal

The maximum number of NUMA nodes for C4 running on the Emerald Rapids CPU platform is 4. For the Granite Rapids CPU platform, the maximum number of NUMA nodes is 6."

C4 standard

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains4 Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4-standard-2 2 7 No 1 shared Up to 10 N/A
c4-standard-4 4 15 No 1 shared Up to 23 N/A
c4-standard-8 8 30 No 1 shared Up to 23 N/A
c4-standard-16 16 60 No 1 shared Up to 23 N/A
c4-standard-24 24 90 No 1 shared Up to 23 N/A
c4-standard-32 32 120 No 1 shared Up to 23 N/A
c4-standard-48 48 180 No 1 isolated Up to 34 Up to 50
c4-standard-96 96 360 No 2 isolated Up to 67 Up to 100
c4-standard-144 144 540 No 3 isolated Up to 100 Up to 150
c4-standard-192 192 720 No 4 (full machine on EMR, not on GNR5) Up to 100 Up to 200
c4-standard-288 288 1,080 No 6 (full machine) Up to 100 Up to 200
c4-standard-288-metal 288 1,080 No 6 (full machine on GNR5) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.
4 The "NUMA domains" column in the tables shows the number of vNUMA nodes exposed to the guest OS.
5 GNR stands for Granite Rapids, Intel's 6th generation Xeon Scalable processor. EMR stands for Emerald Rapids, Intel's 5th generation Xeon Scalable processor.

C4 highcpu

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains4 Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4-highcpu-2 2 4 No 1 shared Up to 10 N/A
c4-highcpu-4 4 8 No 1 shared Up to 23 N/A
c4-highcpu-8 8 16 No 1 shared Up to 23 N/A
c4-highcpu-16 16 32 No 1 shared Up to 23 N/A
c4-highcpu-24 24 48 No 1 shared Up to 23 N/A
c4-highcpu-32 32 64 No 1 shared Up to 23 N/A
c4-highcpu-48 48 96 No 1 isolated Up to 34 Up to 50
c4-highcpu-96 96 192 No 2 isolated Up to 67 Up to 100
c4-highcpu-144 144 288 No 3 isolated Up to 100 Up to 150
c4-highcpu-192 192 384 No 4 (full machine on EMR, not on GMR5) Up to 100 Up to 200
c4-highcpu-288 288 576 No 6 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.
4 The "NUMA domains" column in the tables shows the number of vNUMA nodes exposed to the guest OS.
5 GNR stands for Granite Rapids, Intel's 6th generation Xeon Scalable processor. EMR stands for Emerald Rapids, Intel's 5th generation Xeon Scalable processor.

C4 highmem

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains4 Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4-highmem-2 2 15 No 1 shared Up to 10 N/A
c4-highmem-4 4 31 No 1 shared Up to 23 N/A
c4-highmem-8 8 62 No 1 shared Up to 23 N/A
c4-highmem-16 16 124 No 1 shared Up to 23 N/A
c4-highmem-24 24 186 No 1 shared Up to 23 N/A
c4-highmem-32 32 248 No 1 shared Up to 23 N/A
c4-highmem-48 48 372 No 1 isolated Up to 34 Up to 50
c4-highmem-96 96 744 No 2 isolated Up to 67 Up to 100
c4-highmem-144 144 1,116 No 3 isolated Up to 100 Up to 150
c4-highmem-192 192 1,488 No 4 (full machine on EMR, not on GNR5) Up to 100 Up to 200
c4-highmem-288 288 2,232 No 6 (full machine) Up to 100 Up to 200
c4-highmem-288-metal 288 2,232 No 6 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.
4 The "NUMA domains" column in the tables shows the number of vNUMA nodes exposed to the guest OS.
5 GNR stands for Granite Rapids, Intel's 6th generation Xeon Scalable processor. EMR stands for Emerald Rapids, Intel's 5th generation Xeon Scalable processor.

C4 standard

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains4 Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4-standard-4-lssd 4 15 (1 x 375 GiB) 375 GiB 1 shared Up to 23 N/A
c4-standard-8-lssd 8 30 (1 x 375 GiB) 375 GiB 1 shared Up to 23 N/A
c4-standard-16-lssd 16 60 (2 x 375 GiB) 750 GiB 1 shared Up to 23 N/A
c4-standard-24-lssd 24 90 (4 x 375 GiB) 1,500 GiB 1 shared Up to 23 N/A
c4-standard-32-lssd 32 120 (5 x 375 GiB) 1,875 GiB 1 shared Up to 23 N/A
c4-standard-48-lssd 48 180 (8 x 375 GiB) 3,000 GiB 1 isolated Up to 34 N/A
c4-standard-96-lssd 96 360 (16 x 375 GiB) 6,000 GiB 2 isolated Up to 67 N/A
c4-standard-144-lssd 144 540 (24 x 375 GiB) 9,000 GiB 3 isolated Up to 100 N/A
c4-standard-192-lssd 192 720 (32 x 375 GiB) 12,000 GiB 4 isolated Up to 100 N/A
c4-standard-288-lssd 288 1,080 (48 x 375 GiB) 18,000 GiB 6 (full machine) Up to 100 Up to 200
c4-standard-288-lssd-metal 288 1,080 (6 x 3,000 GiB) 18,000 GiB 6 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.
4 The "NUMA domains" column in the tables shows the number of vNUMA nodes exposed to the guest OS.
5 GNR stands for Granite Rapids, Intel's 6th generation Xeon Scalable processor. EMR stands for Emerald Rapids, Intel's 5th generation Xeon Scalable processor.

C4 highmem

Machine types vCPUs1 Memory (GB) Titanium SSD NUMA domains4 Default egress bandwidth (Gbps)2 Tier_1 egress bandwidth (Gbps)3
c4-highmem-4-lssd 4 31 (1 x 375 GiB) 375 GiB 1 shared Up to 23 N/A
c4-highmem-8-lssd 8 62 (1 x 375 GiB) 375 GiB 1 shared Up to 23 N/A
c4-highmem-16-lssd 16 124 (2 x 375 GiB) 750 GiB 1 shared Up to 23 N/A
c4-highmem-24-lssd 24 186 (4 x 375 GiB) 1,500 GiB 1 shared Up to 23 N/A
c4-highmem-32-lssd 32 248 (5 x 375 GiB) 1,875 GiB 1 shared Up to 23 N/A
c4-highmem-48-lssd 48 372 (8 x 375 GiB) 3,000 GiB 1 isolated Up to 34 N/A
c4-highmem-96-lssd 96 744 (16 x 375 GiB) 6,000 GiB 2 isolated Up to 67 N/A
c4-highmem-144-lssd 144 1,116 (24 x 375 GiB) 9,000 GiB 3 isolated Up to 100 N/A
c4-highmem-192-lssd 192 1,488 (32 x 375 GiB) 12,000 GiB 4 isolated Up to 100 N/A
c4-highmem-288-lssd 288 2,232 (48 x 375 GiB) 18,000 GiB 6 (full machine) Up to 100 Up to 200
c4-highmem-288-lssd-metal 288 2,232 (6 x 3,000 GiB) 18,000 GiB 6 (full machine) Up to 100 Up to 200

1 A CPU uses two threads per core, and a vCPU represents a single thread. See CPU platforms.
2 Default egress bandwidth can't exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
3 Supports high-bandwidth networking for larger machine types.
4 The "NUMA domains" column in the tables shows the number of vNUMA nodes exposed to the guest OS.
5 GNR stands for Granite Rapids, Intel's 6th generation Xeon Scalable processor. EMR stands for Emerald Rapids, Intel's 5th generation Xeon Scalable processor.

C4 doesn't support custom machine types.

Supported disk types for C4

C4 VMs support only the NVMe disk interface and can use the following Hyperdisk block storage:

VM instances

  • Hyperdisk Balanced (hyperdisk-balanced)
  • Hyperdisk Balanced High Availability (hyperdisk-balanced-high-availability)
  • Hyperdisk Throughput (hyperdisk-throughput)
  • Hyperdisk Extreme (hyperdisk-extreme)
  • Local SSD (only available with -lssd machine types)

Bare metal instances

  • Hyperdisk Balanced (hyperdisk-balanced)
  • Hyperdisk Extreme (hyperdisk-extreme)
  • Local SSD (only available with -lssd-metal machine types)

C4 doesn't support Persistent Disk. When upgrading to a newer machine series, to migrate your Persistent Disk resources to Hyperdisk, see Move your workload from an existing VM to a new VM.

Disk and capacity limits

You can attach a mixture of different Hyperdisk types to an instance, but 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

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

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

C4 standard

Maximum number of disks
Machine types Hyperdisk
per VM