Compute-optimized instances are ideal for compute-intensive and high performance computing (HPC) workloads. Compute-optimized instances offer the highest performance per core and are built on architecture that utilizes features like non-uniform memory access (NUMA) for optimal reliable uniform performance.
Note: For the C3 and C3D machine series, see General-purpose machine family. H3 machine seriesH3 instances are powered by the 4th generation Intel Xeon Scalable processors (code-named Sapphire Rapids), DDR5 memory, and Titanium offload processors.
H3 instances offer the best price performance for compute-intensive high performance computing (HPC) workloads in Compute Engine. H3 instances are single-threaded and are ideal for a variety of modeling and simulation workloads including computational fluid dynamics, crash safety, genomics, financial modeling, and general scientific and engineering computing. H3 instances support compact placement, which is optimized for tightly-coupled applications that scale across multiple nodes.
The H3 series is available in one size, comprising an entire host server. To save on licensing costs, you can customize the number of visible cores, but you are charged the same price for the instance. H3 instances can use the entire host network bandwidth and come with a default network bandwidth rate of up to 200 Gbps. However, the instance to internet bandwidth is limited to 1 Gbps.
Simultaneous multithreading (SMT) is disabled for H3 instances and can't be enabled. There is also no overcommitting to ensure optimal performance consistency.
H3 instances are available on-demand, or with one- and three-year committed use discounts (CUDs). H3 instances can be used with Google Kubernetes Engine.
H3 LimitationsThe H3 machine series has the following restrictions:
H3 instances are available as a predefined configuration with 88 vCPUs and 352 GB of memory.
Machine types vCPUs* Memory (GB) Local SSD Default egressh3-standard-88 88 352 Not supported Up to 200 Gbps
* A vCPU represents an entire core—no simultaneous multithreading (SMT).
† Default egress bandwidth cannot exceed the number given. Actual egress bandwidth depends on the destination IP address and other factors. See Network bandwidth.
H3 instances can use the following block storage types:
pd-balanced)hyperdisk-balanced)hyperdisk-throughput)If supported by the machine type, you can use a mixture of Hyperdisk and Persistent Disk volumes on a VM, but the following restrictions apply:
The maximum total disk capacity (in TiB) across all disk types can't exceed:
For details about the capacity limits, see Hyperdisk size and attachment limits and Persistent Disk maximum capacity.
H3 storage limits are described in the following table:
Maximum number of disks per instance Machine types All disk types * All Hyperdiskh3-standard-88 128 64 8 64 0
This limit applies to Persistent Disk and Hyperdisk, but doesn't include Local SSD disks.
Network support for H3 instancesH3 VMs require gVNIC network interfaces. H3 supports up to 200 Gbps network bandwidth for standard networking.
Before migrating to H3 or creating H3 instances, make sure that the operating system image that you use supports the gVNIC driver. To get the best possible performance on H3 instances, on the Networking features tab of the OS details table, 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 H3 instance is using an operating system with an older version of the gVNIC driver, this is still supported but the instance might experience suboptimal performance such as less network bandwidth or higher latency.
If you use a custom OS image with the H3 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 H3 instances. Google recommends using the latest gVNIC driver version to benefit from additional features and bug fixes.
Maintenance experience for H3 instancesDuring the lifecycle of a Compute Engine instance, the host machine that your instance runs on 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 H3 machine series offers the following features related to host maintenance:
The maintenance frequencies shown in the previous table are approximations, not guarantees. Compute Engine might occasionally perform maintenance more frequently.
C2D machine seriesThe C2D machine series provides the largest instance sizes and are best-suited for high performance computing (HPC). The C2D series also has the largest available last-level cache (LLC) cache per core.
The C2D machine series comes in different machine types ranging from 2 to 112 vCPUs, and offer up to 896 GB of memory. You can attach up to 3 TiB of Local SSD storage to these machine types for applications that require higher storage performance.
The C2D series supports these compute-bound workloads by using the third generation AMD EPYC Milan platform.
The C2D series supports Confidential VM.
C2D LimitationsThe C2D machine series has the following restrictions:
C2D instances are available as predefined configurations in sizes ranging from 2 vCPUs to 112 vCPUs and up to 896 GB of memory.
highmem: 8 GB memory per vCPU
c2d-standard-2 2 8 1, 2, 4, or 8 Up to 10 N/A c2d-standard-4 4 16 1, 2, 4, or 8 Up to 10 N/A c2d-standard-8 8 32 1, 2, 4, or 8 Up to 16 N/A c2d-standard-16 16 64 1, 2, 4, or 8 Up to 32 N/A c2d-standard-32 32 128 2, 4, or 8 Up to 32 Up to 50 c2d-standard-56 56 224 4 or 8 Up to 32 Up to 50 c2d-standard-112 112 448 8 Up to 32 Up to 100
* A vCPU represents a single logical CPU thread. See CPU platforms.
† Default egress bandwidth cannot 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.
# Number of 375 GiB Local SSD disks that you can choose to add when creating the instance.
c2d-highcpu-2 2 4 1, 2, 4, or 8 Up to 10 N/A c2d-highcpu-4 4 8 1, 2, 4, or 8 Up to 10 N/A c2d-highcpu-8 8 16 1, 2, 4, or 8 Up to 16 N/A c2d-highcpu-16 16 32 1, 2, 4, or 8 Up to 32 N/A c2d-highcpu-32 32 64 2, 4, or 8 Up to 32 Up to 50 c2d-highcpu-56 56 112 4 or 8 Up to 32 Up to 50 c2d-highcpu-112 112 224 8 Up to 32 Up to 100
* A vCPU represents a single logical CPU thread. See CPU platforms.
† Default egress bandwidth cannot 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.
# Number of 375 GiB Local SSD disks that you can choose to add when creating the instance.
c2d-highmem-2 2 16 1, 2, 4, or 8 Up to 10 N/A c2d-highmem-4 4 32 1, 2, 4, or 8 Up to 10 N/A c2d-highmem-8 8 64 1, 2, 4, or 8 Up to 16 N/A c2d-highmem-16 16 128 1, 2, 4, or 8 Up to 32 N/A c2d-highmem-32 32 256 2, 4, or 8 Up to 32 Up to 50 c2d-highmem-56 56 448 4 or 8 Up to 32 Up to 50 c2d-highmem-112 112 896 8 Up to 32 Up to 100
* A vCPU represents a single logical CPU thread. See CPU platforms.
† Default egress bandwidth cannot 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.
# Number of 375 GiB Local SSD disks that you can choose to add when creating the instance.
C2D instances can use the following block storage types:
pd-standard)pd-balanced)pd-ssd)Each C2D instance can have a maximum of 128 Persistent Disk volumes (including the boot disk) attached to the instance, and a total of 257 GiB disk capacity.
C2D instances with Confidential Computing running Microsoft Windows with the NVMe disk interface have a disk attachment limitation of 16 disks. See Known issues for details.
Note: Persistent Disk usage is charged separately from machine type pricing. Network support for C2D instancesThe C2D machine types support either the VirtIO or gVNIC network driver. C2D instances with 32 or more vCPUS support higher network bandwidths of 50 Gbps and 100 Gbps with gVNIC and per VM Tier_1 networking performance.
Maintenance experience for C2D instancesDuring the lifecycle of a Compute Engine instance, the host machine that your instance runs on 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 C2D machine series offers the following features related to host maintenance:
The maintenance frequencies shown in the previous table are approximations, not guarantees. Compute Engine might occasionally perform maintenance more frequently.
C2 machine seriesThe C2 machine series provides full transparency into the architecture of the underlying server platforms, letting you fine-tune the performance. Machine types in this series offer much more computing power, and are generally more robust for compute-intensive workloads compared to N1 high-CPU machine types.
The C2 series comes in different machine types ranging from 4 to 60 vCPUs, and offers up to 240 GB of memory. You can attach up to 3 TiB of Local SSD storage to these instances for applications that require higher storage performance.
This series also produces a greater than 40% performance improvement compared to the previous generation N1 machines and offer higher performance per thread and isolation for latency-sensitive workloads.
The C2 series enables the highest performance per core and the highest frequency for compute-bound workloads using Intel 3.9 GHz Cascade Lake processors. If you are looking to optimize workloads for single thread performance, particularly with respect to floating point, choose a machine type in this series to take advantage of AVX-512 capabilities only available on Intel.
C2 LimitationsThe C2 machine series has the following restrictions:
C2 instances are available as predefined configurations with 4 to 60 vCPUs and 4 GB memory per vCPU.
Machine types vCPUs* Memory (GB) Local SSD# Default egressc2-standard-4 4 16 1, 2, 4, or 8 Up to 10 N/A c2-standard-8 8 32 1, 2, 4, or 8 Up to 16 N/A c2-standard-16 16 64 2, 4, or 8 Up to 32 N/A c2-standard-30 30 120 4 or 8 Up to 32 Up to 50 c2-standard-60 60 240 8 Up to 32 Up to 100
*A vCPU represents a single logical CPU thread. See CPU platforms.
† Default egress bandwidth cannot 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.
C2 instances can use the following block storage types:
pd-standard)pd-balanced)pd-ssd)Each C2 instance can have a maximum of 128 Persistent Disk volumes (including the boot disk) attached to the instance, and a total of 257 GiB disk capacity.
Note: Persistent Disk usage is charged separately from machine type pricing. Network support for C2 instancesThe C2 machine types support either the VirtIO or gVNIC network driver. C2 instances with 30 or more vCPUS support higher network bandwidths of 50 Gbps and 100 Gbps with gVNIC and per VM Tier_1 networking performance.
Maintenance experience for C2 instancesDuring the lifecycle of a Compute Engine instance, the host machine that your instance runs on 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 C2 machine series offers the following features related to host maintenance:
The maintenance frequencies shown in the previous table are approximations, not guarantees. Compute Engine might occasionally perform maintenance more frequently.
What's nextRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3