Preview of Confidential VMs running with AMD SEV on C4D machines
With Google’s Titanium hardware, the C4D machine series provides optimal, dependable, and consistent performance with its 5th-generation AMD EPYC (code-named Turin) CPUs.
Google Cloud now provides Confidential Compute on AMD machine families like N2D, C2D, and C3D that are available worldwide. It is announced that the general-purpose C4D machine series’ confidential virtual machines (VMs) with AMD Secure Encrypted Virtualization (AMD SEV) technology are in preview today and will shortly be made widely available.
The fifth generation AMD EPYC Turin processor and Titanium power C4D virtual machines. C4D outperforms C3D by 30% on the predicted SPECrate2017_int_base benchmark, allowing you to grow performance with fewer resources and maximising your expenses.
Web, app, and game servers, AI inference, web serving, video streaming, data-centric applications like analytics, and relational and in-memory databases are among the workloads that C4D is built to handle.
C4D’s greater core frequency (up to 4.1 GHz) and better Instructions Per Clock (IPC) allow it to perform 38% more operations per second for Memorystore for Redis workloads and 56% more queries per second on Cloud SQL for MySQL than C3D.
With AMD EPYC Turin, web-serving workloads can achieve up to 80% better throughput per vCPU with C4D, with improvements in branch prediction and L3-cache efficiency.
C4D machine series features
To summarize, the following characteristics are present in the C4D machine series:
- Titanium and the AMD EPYC Turin CPU power it.
- Up to 384 virtual CPUs and 3,024 GB of DDR5 memory are supported.
- Local Titanium SSD discs up to 12,000 GiB in size are supported.
- Provides a choice of preconfigured machine types with sizes ranging from 2 to 384 virtual central chips.
- Supports alternatives for consumption such as future bookings, Spot VMs, and on-demand
- Allows for typical network setup with a maximum bandwidth of 100 Gbps.
- Supports networking performance at up to 200 Gbps per virtual machine (VM) Tier 1.
- Only accommodates HyperDisk volumes.
- Supports AMD SEV for Confidential Virtual Machines Flexible and resource-based committed use discounts
- Supports policies for compact and dispersed placement.
Types of C4D machine series
C4D virtual machines come in regular, high-cpu, and high-mem sizes, with predefined configurations that range from 2 vCPU to 384 vCPUs and up to 3,024 GB of memory.
Use the -lssd option of the C4D machine types to construct your instance in order to use Titanium SSD with C4D. An instance of the desired size with Titanium SSD partitions attached is created when this machine type is selected. Volumes of Titanium SSDs cannot be connected separately.
C4D is not compatible with custom machine types.
Supported disk types for C4D Virtual machines (VMs)
It can utilize the following Hyperdisk block storage and only support the NVMe disk interface:
- Hyperdisk Steady (hyperdisk-steady)
- Extreme Hyperdisk (also known as hyperdisk-extreme)
- With the -lssd option, local titanium SSD is automatically added to certain system kinds.
C4D is not compatible with Persistent Disc.
Disk and capacity limits
Although you can utilise a variety of different types of hyperdisks with a virtual machine (VM), the total disc capacity (in TiB) of all disc types cannot be greater than:
- All hyperdisks have 257 TiB for system types with fewer than 32 vCPUs.
- For several kinds of machines with 32 vCPUs or other 512 TiB for the entire hyperdisk
Network support for C4D machines
Network interfaces for C4D virtual machines must be gVNIC. For normal networking, C4D can handle network bandwidth of up to 100 Gbps, and for per-VM Tier_1 networking performance, it can handle up to 200 Gbps.
Be certain that the operating system image you are using supports the gVNIC driver before moving to C4D or starting C4D instances. For best performance on C4D instances, choose an OS image that supports both “Tier_1 Networking” and “200 Gbps network bandwidth” on the Networking features tab of the OS information table. Although the guest OS shows the gve driver version as 1.0.0, the gVNIC driver is upgraded in these images. Although your C4D instance may still function properly if it is running an operating system with an outdated gVNIC driver, it may perform less well than it should, for example, by having more latency or less network bandwidth.
You can manually install the latest gVNIC driver if you use a custom OS image with the C4D machine series. When using C4D instances, the gVNIC driver version v1.3.0 or later is advised. Google advises using the most recent version of the gVNIC driver in order to take advantage of new features and problem fixes.
You can also read How GCP Confidential Computing develops trusted AI
Thank you for your Interest in Cloud Computing. Please Reply