---
name: vpc-vsi_is_profiles
title: x86-64 instance profiles
description: A profile is a combination of instance attributes, such as the number of vCPUs, amount of RAM, network bandwidth, and default bandwidth allocation. The attributes define the size and capabilities of the virtual server instance that is provisioned. In the IBM Cloud console, you can select the most recently used profile or click **View All Profiles** to choose the profile that best fits your needs.
last-updated: 2026-07-20
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vpc?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# x86-64 instance profiles
{: #profiles}

When you provision IBM Cloud&reg; Virtual Servers for Virtual Private Cloud, you can select from ten families of profiles: Balanced, Compute, Memory, Very High Memory, Ultra High Memory, GPU, Storage Optimized, Confidential Computing, Flex, and High Frequency.

A profile is a combination of instance attributes, such as the number of vCPUs, amount of RAM, network bandwidth, and default bandwidth allocation. The attributes define the size and capabilities of the virtual server instance that is provisioned. In the IBM Cloud console, you can select the most recently used profile or click **View All Profiles** to choose the profile that best fits your needs.
{: shortdesc}

For more information about SAP profiles, see [SAP HANA certified instances on Intel-powered virtual servers on VPC Infrastructure](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-vpc-intel-vsi&format=markdown) and [SAP Application Server certified instances on Intel-powered virtual servers on VPC Infrastructure](https://cloud.ibm.com/docs/sap?topic=sap-nw-iaas-offerings-profiles-vpc-vsi&format=markdown).

## Before you begin
{: #x86-64-instance-profiles-before-you-begin}

Verify the profile that you use is available in the zone where you plan to create the instance.

Some profiles might not be available because of one of the following reasons:
   - The number of network interfaces in the virtual server exceeds profile limits. You can remove network interfaces to select from more profiles. For more information, see [Resizing a virtual server](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance&format=markdown).
   - The selected image contains an allowed-use expression that is not compatible with the profile. In these cases, select an image with an allowed-use expression that is compatible with the selected profile. For more information, see [Adding allowed-use expressions to custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-custom-image-allowed-use-expressions&interface=ui&format=markdown).

## Profile families
{: #x86-64-instance-profile-families}

The following profile families are available when you provision a virtual server instance.

| Family | Description |
| -------- | ----------- |
| [Balanced](#balanced) | Balanced profiles offer a core to RAM ratio that is best for midsize databases and common cloud applications with moderate traffic. |
| [Compute](#compute)  | Compute profiles offer a core to RAM ratio that is best for moderate to high web traffic workloads. Compute profiles are best for workloads with intensive CPU demands, such as high web traffic workloads, production batch processing, and front-end web servers. |
| [Memory](#memory) | Memory profiles offer a core to RAM ratio that is best for memory caching and real-time analytics workloads. Memory profiles are best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads. |
| [Very High Memory](#vhmemory) | Very High Memory profiles offer a core to RAM ratio of 1 vCPU to 14 GiB of RAM. This family is optimized for running small to medium in-memory databases and OLAP workloads, such as SAP BW/4 HANA. |
| [Ultra High Memory](#uhmemory) | Ultra High Memory profiles offer the most memory per core with 1 vCPU to 28 GiB of RAM. These profiles are optimized to run large in-memory databases and OLTP workloads, such as SAP S/4 HANA.|
| [GPU](#gpu) | GPU-enabled profiles provide on-demand access to GPUs and accelerators to facilitate AI, high-performance computing, data science, and graphics workloads.|
| [Storage Optimized](#storageopt) | Storage Optimized profiles offer temporary SSD instance storage disks at a ratio of 1 vCPU to 300 GB instance storage with a smaller price point per GB. These profiles are designed for storage-dense workloads and offer `virtio` interface type for attached disks. |
| [Confidential Compute](#confidential-computing-profiles) | Confidential Compute-supported profiles use processor reserved memory called EPC (Enclave Page Cache) to encrypt application data. Processor reserved memory EPC maintains confidentiality and integrity. |
| [Flex profiles](#flexible-profiles) | Flex profiles offer a cost-effective option to help improve and mainstream capacity and scalability where and when you need it. |
| [Burstable Flex profiles](#burstable-supported-flex-profiles) | Burstable profiles are designed to provide flexible CPU performance so workloads can operate at a smaller baseline level and burst to higher performance when needed. |
| [High Frequency profiles](#high-frequency-profiles) (select availability) | High Frequency profiles provide CPUs with a high frequency, which generally enables higher performance per core than other profiles within the same hardware generation.|
{: caption="Virtual server family selections" caption-side="bottom"}

2nd generation profiles with instance storage and 2nd generation profiles with 64 or more vCPUs are deployed exclusively on the Intel&reg; second-generation quad processor Xeon&reg; Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or an Intel quad processor Xeon Gold 6248 Cascade Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.
{: note}

[Deprecated]{: tag-deprecated} For more information about LinuxONE (s390x processor architecture) profiles, see [s390x instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-vs-profiles&interface=ui&format=markdown).

Profiles with AMD-manufactured processors are available in the Toronto region.
{: preview}

## Balanced
{: #balanced}

Balanced profiles provide a mix of performance and scalability for more common workloads. The Balanced profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown). The following table shows all Balanced profiles that are available for Intel&reg; x86-64, and AMD x86-64 processors.

The 4th generation balanced profiles (bx4) are available in the Dallas (us-south) region. For more information about the capabilities of the new profiles, see [General purpose instance profiles - Intel Gen 4](https://cloud.ibm.com/docs/vpc?topic=vpc-general-purpose-vsi-profiles-gen4-intel&interface=ui&format=markdown).
{: preview}

The following table shows all balance profiles that are available for x86-64.

| Instance profile | vCPU / Cores | NUMA count | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|-------|-------|---------|---------|
| bx3d-2x10 | 2 / 1 | 1 | 10 | 4 | 1x65 |
| bx3d-4x20 | 4 / 2 | 1 | 20 | 8 | 1x130 |
| bx3d-8x40 | 8 / 4 | 1 | 40 | 16 | 1x260 |
| bx3d-16x80 | 16 / 8 |  1 | 80 | 32 | 1x520 |
| bx3d-24x120 | 24 / 12 | 1 | 120 | 48 | 1x780 |
| bx3d-32x160 | 32 / 16 | 2 | 160 | 64 | 2x520 |
| bx3d-48x240 | 48 / 24 | 2 | 240 | 96 | 2x780 |
| bx3d-64x320 | 64 / 32 | 2 | 320 | 128 | 2x1024 |
| bx3d-96x480 | 96 / 48 | 2 | 480 | 192 | 2x1560 |
| bx3d-128x640 | 128 / 64 | 2 | 640 | 200 | 2x2080 |
| bx3d-176x880 | 176 / 88 | 2 | 880 | 200 | 2x2860 |
{: caption="Balanced bx3 profile options for Intel x86-64 instances" caption-side="bottom"}
{: #balanced-intel-x86-64-spr}
{: tab-title="bx3"}
{: tab-group="Balanced"}
{: class="simple-tab-table"}
{: summary="Balanced Beta profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|
| bx2-2x8 | 2 / 1 | 8 | 4 | - |
| bx2d-2x8 | 2 / 1 | 8 | 4 | 1x75 |
| bx2-4x16 | 4 / 2 | 16 | 8 | - |
| bx2d-4x16 | 4 / 2 | 16 | 8 | 1x150 |
| bx2-8x32 | 8 / 4 | 32 | 16 | - |
| bx2d-8x32 | 8 / 4 | 32 | 16 | 1x300 |
| bx2-16x64 | 16 / 8 | 64 | 32 | - |
| bx2d-16x64 | 16 / 8 | 64 | 32 | 1x600 |
| bx2-32x128 | 32 / 16 | 128 | 64 | - |
| bx2d-32x128 | 32 / 16 | 128 | 64 | 2x600 |
| bx2-48x192 | 48 / 24 | 192 | 80 | - |
| bx2d-48x192 | 48 / 24 | 192 | 80 | 1x900 |
| bx2-64x256 | 64 / 32 | 256| 80 | - |
| bx2d-64x256 | 64 / 32 | 256 | 80 | 2x1200 |
| bx2-96x384 | 96 / 48 | 384 | 80 | - |
| bx2d-96x384 | 96 / 48 | 384 | 80 | 2x1800 |
| bx2-128x512 | 128 / 64 | 512 | 80 | - |
| bx2d-128x512 | 128 / 64 | 512 | 80 | 2x2400 |
| bx2a-2x8 | 2 / 1 | 8 | 2 | - |
| bx2a-4x16 | 4 / 2 |  16 | 4 | - |
| bx2a-8x32 | 8 / 4 | 32 | 8 | - |
| bx2a-16x64 | 16 / 8 | 64 | 16 | - |
| bx2a-32x128 | 32 / 16 | 128 | 32 | - |
| bx2a-48x192 | 48 / 24 | 192 | 48 | - |
| bx2a-64x256 | 64 / 32 | 256 | 64 | - |
| bx2a-96x384 | 96 / 48 | 384 | 80 | - |
| bx2a-128x512 | 128 / 64 | 512 | 80 | - |
| bx2a-228x912 | 228 / 114 | 912 | 80 | - |
{: caption="Balanced bx2 profile options for Intel x86-64 instances" caption-side="bottom"}
{: #balanced-intel-x86-64}
{: tab-title="bx2"}
{: tab-group="Balanced"}
{: class="simple-tab-table"}
{: summary="Balanced bx2 profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | NUMA count | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| bx4-2x8 | 2 / 1 | 1 | 8 | 4 | - |
| bx4d-2x8 | 2 / 1 | 1 | 8 | 4 | 1x65 |
| bx4-4x16 | 4 / 2 | 1 | 16 | 8 | - |
| bx4d-4x16 | 4 / 2 | 1 | 16 | 8 | 1x130 |
| bx4-8x32 | 8 / 4 | 1 | 32 | 16 | - |
| bx4d-8x32 | 8 / 4 | 1 | 32 | 16 | 1x260 |
| bx4-16x64 | 16 / 8 | 1 | 64 | 32 | - |
| bx4d-16x64 | 16 / 8 | 1 | 64 | 32 | 1x520 |
| bx4-24x96 | 24 / 12 | 1 | 96 | 48 | - |
| bx4d-24x96 | 24 / 12 | 1 | 96 | 48 | 1x780 |
| bx4-32x128 | 32 / 16 | 1 | 128 | 64 | - |
| bx4d-32x128 | 32 / 16 | 1 | 128 | 64 | 2x520 |
| bx4-48x192 | 48 / 24 | 1 | 192 | 96 | - |
| bx4d-48x192 | 48 / 24 | 1 | 192 | 96 | 2x780 |
| bx4-64x256 | 64 / 32 | 2 | 256| 128 | - |
| bx4d-64x256 | 64 / 32 | 2 | 256 | 128 | 2x780 |
| bx4-96x384 | 96 / 48 | 2 | 384 | 192 | - |
| bx4d-96x384 | 96 / 48 | 2 | 384 | 192 | 2x780 |
| bx4-128x512 | 128 / 64 | 2 | 512 | 200 | - |
| bx4d-128x512 | 128 / 64 | 2 | 512 | 200 | 2x780 |
| bx4-176x704 | 176 / 88 | 2 | 704 | 200 | - |
| bx4d-176x704 | 176 / 88 | 2 | 704 | 200 | 2x780 |
{: caption="Balanced bx4 profile options for Intel x86-64 instances" caption-side="bottom"}
{: #balanced-intel-x86-64-gen4}
{: tab-title="bx4 (Select availability)"}
{: tab-group="Balanced"}
{: class="simple-tab-table"}
{: summary="Balanced bx4 profile options for Intel x86-64 virtual server instances."}

AMD-based virtual machines use AMD EPYC Milan processors. Compute capabilities are limited to AMD EPYC Rome capabilities.
{: important}

## Compute
{: #compute}

Compute profiles are best for workloads with intensive CPU demands, such as high web traffic workloads, production batch processing, and front-end web servers. The Compute profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown). The following table shows all Compute profiles that are available for &reg; x86-64.

The 4th generation compute profiles (cx4) are available in the Dallas (us-south) region. For more information about the capabilities of the new profiles, see [General purpose instance profiles - Intel Gen 4](https://cloud.ibm.com/docs/vpc?topic=vpc-general-purpose-vsi-profiles-gen4-intel&interface=ui&format=markdown).
{: preview}

The following table shows all compute profiles that are available for x86-64.

| Instance profile | vCPU / Cores | NUMA count | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| cx3d-2x5 | 2 / 1 | 1 | 5 | 4 | 1x65 |
| cx3d-4x10 | 4 / 2 | 1 | 10 | 8 | 1x130 |
| cx3d-8x20 | 8 / 4 | 1 | 20 | 16 | 1x260 |
| cx3d-16x40 | 16 / 8 | 1 | 40 | 32 | 1x520 |
| cx3d-24x60 | 24 / 12 | 1 | 60 | 48 | 1x780 |
| cx3d-32x80 | 32 / 16 | 2 | 80 | 64 | 2x520 |
| cx3d-48x120 | 48 / 24 | 2 |  120 | 96 | 2x780 |
| cx3d-64x160 | 64 / 32 | 2 | 160 | 128 | 2x1024 |
| cx3d-96x240 | 96 / 48 | 2 | 240 | 192 | 2x1560 |
| cx3d-128x320 | 128 / 64  | 2 | 320 | 200 | 2x2080 |
| cx3d-176x440 | 176 / 88 | 2 | 440 | 200 | 2x2860 |
{: caption="Compute profile options for x86-64 instances" caption-side="bottom"}
{: #compute-intel-x86-64}
{: tab-title="cx3d"}
{: tab-group="Compute"}
{: class="simple-tab-table"}
{: summary="3rd generation Compute profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|
| cx2-2x4 | 2 / 1 | 4 | 4 | - |
| cx2d-2x4 | 2 / 1 | 4 | 4 | 1x75 |
| cx2-4x8 | 4 / 2 | 8 | 8 | - |
| cx2d-4x8 | 4 / 2 | 8 | 8 | 1x150 |
| cx2-8x16 | 8 / 4 | 16 | 16 | - |
| cx2d-8x16 | 8 / 4 | 16 | 16 | 1x300 |
| cx2-16x32 | 16 / 8 |  32 | 32 | - |
| cx2d-16x32 | 16 / 8 | 32 | 32 | 1x600 |
| cx2-32x64 | 32 / 16 | 64 | 64 | - |
| cx2d-32x64 | 32 / 16 | 64 | 64 | 2x600 |
| cx2-48x96 | 48 / 24 | 96 | 80 | - |
| cx2d-48x96 | 48 / 24 | 96 | 80 | 1x900 |
| cx2-64x128 | 64 / 32 | 128 | 80 | - |
| cx2d-64x128 | 64 / 32 | 128 | 80 | 2x1200 |
| cx2-96x192 | 96 / 48 | 192 | 80 | - |
| cx2d-96x192 | 96 / 48 | 192 | 80 | 2x1800 |
| cx2-128x256 | 128 / 64 | 256 | 80 | - |
| cx2d-128x256 | 128 / 64 | 256 | 80 | 2x2400 |
{: caption="Compute profile options for x86-64 instances" caption-side="bottom"}
{: #compute-intel-x86-64b}
{: tab-title="cx2"}
{: tab-group="Compute"}
{: class="simple-tab-table"}
{: summary="Compute profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | NUMA count |GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| cx4-2x4 | 2 / 1 | 1 | 4 | 4 | - |
| cx4d-2x4 | 2 / 1 | 1 | 4 | 4 | 1x65 |
| cx4-4x8 | 4 / 2 | 1 | 8 | 8 | - |
| cx4d-4x8 | 4 / 2 | 1 | 8 | 8 | 1x130 |
| cx4-8x16 | 8 / 4 | 1 | 16 | 16 | - |
| cx4d-8x16 | 8 / 4 | 1 | 16 | 16 | 1x260 |
| cx4-16x32 | 16 / 8 | 1 |  32 | 32 | - |
| cx4d-16x32 | 16 / 8 | 1 | 32 | 32 | 1x520 |
| cx4-24x48 | 24 / 12 | 1 |  48 | 48 | - |
| cx4d-24x48 | 24 / 12 | 1 | 48 | 48 | 1x780 |
| cx4-32x64 | 32 / 16 | 1 | 64 | 64 | - |
| cx4d-32x64 | 32 / 16 | 1 | 64 | 64 | 2x520 |
| cx4-48x96 | 48 / 24 | 1 | 96 | 96 | - |
| cx4d-48x96 | 48 / 24 | 1 | 96 | 96 | 2x780 |
| cx4-64x128 | 64 / 32 | 2 | 128 | 128 | - |
| cx4d-64x128 | 64 / 32 | 2 | 128 | 128 | 2x780 |
| cx4-96x192 | 96 / 48 | 2 | 192 | 192 | - |
| cx4d-96x192 | 96 / 48 | 2 | 192 | 192 | 2x780 |
| cx4-128x256 | 128 / 64 | 2 | 256 | 200 | - |
| cx4d-128x256 | 128 / 64 | 2 | 256 | 200 | 2x780 |
| cx4-176x352 | 176 / 88 | 2 | 352 | 200 | - |
| cx4d-176x352 | 176 / 88 | 2 | 352 | 200 | 2x780 |
{: caption="Compute cx4 profile options for x86-64 instances" caption-side="bottom"}
{: #compute-intel-x86-64-gen4}
{: tab-title="cx4 (Select availability)"}
{: tab-group="Compute"}
{: class="simple-tab-table"}
{: summary="Compute cx4 profile options for Intel x86-64 virtual server instances."}

## Memory
{: #memory}

Memory profiles are best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads. The Memory profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown). The following table shows all Memory profiles that are available for Intel&reg; x86-64.

The 4th generation memory profiles (mx4) are available in the Dallas (us-south) region. For more information about the capabilities of the new profiles, see [General purpose instance profiles - Intel Gen 4](https://cloud.ibm.com/docs/vpc?topic=vpc-general-purpose-vsi-profiles-gen4-intel&interface=ui&format=markdown).
{: preview}

| Instance profile | vCPU / Cores | NUMA count | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|-------|-------|---------|---------|---------|
| mx3d-2x20 | 2 / 1 | 1 | 20 | 4 | 1x65 |
| mx3d-4x40 | 4 / 2 | 1 | 40 | 8 | 1x130 |
| mx3d-8x80 | 8 / 4 | 1 | 80 | 16 | 1x260 |
| mx3d-16x160 | 16 / 8 |  1 | 160 | 32 | 1x520 |
| mx3d-24x240 | 24 / 12 | 1 | 240 | 48 | 1x780 |
| mx3d-32x320 | 32 / 16 | 2 | 320 | 64 | 2x520 |
| mx3d-48x480 | 48 / 24 | 2 | 480 | 96 | 2x780 |
| mx3d-64x640 | 64 / 32 | 2 | 640 | 128 | 2x1024 |
| mx3d-96x960 | 96 / 48 | 2 | 960 | 192 | 2x1560 |
| mx3d-128x1280 | 128 / 64 | 2 | 1280 | 200 | 2x2080 |
| mx3d-176x1760 | 176 / 88 | 2 | 1760 | 200 | 2x2860 |
{: caption="Memory mx3 profile options for x86-64 instances " caption-side="bottom"}
{: #memory-intel-x86-64}
{: tab-title="mx3"}
{: tab-group="Memory"}
{: class="simple-tab-table"}
{: summary="Memory mx3d profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|
| mx2-2x16 | 2 / 1 | 16 | 4 | - |
| mx2d-2x16 | 2 / 1 | 16 | 4 | 1x75 |
| mx2-4x32 | 4 / 2 | 32 | 8 | - |
| mx2d-4x32 | 4 / 2 | 32 | 8 | 1x150 |
| mx2-8x64 | 8 / 4 | 64 | 16 | - |
| mx2d-8x64 | 8 / 4 | 64 | 16 | 1x300 |
| mx2-16x128 | 16 / 8 | 128 | 32 | - |
| mx2d-16x128 | 16 / 8 | 128 | 32 | 1x600 |
| mx2-32x256 | 32 / 16 | 256 | 64 | - |
| mx2d-32x256 | 32 / 16 | 256 | 64 | 2x600 |
| mx2-48x384 | 48 / 24 | 384 | 80 | - |
| mx2d-48x384 | 48 / 24 | 384 | 80 | 2x900 |
| mx2-64x512| 64 / 32 | 512 | 80 | - |
| mx2d-64x512| 64 / 32 | 512 | 80 | 2x1200 |
| mx2-96x768| 96 / 48 | 768 | 80 | - |
| mx2d-96x768| 96 / 48 | 768 | 80 | 2x1800 |
| mx2-128x1024| 128 / 64 | 1024 | 80 | - |
| mx2d-128x1024| 128 / 64 | 1024 | 80 | 2x2400 |
{: caption="Memory mx2 profile options for x86-64 instances " caption-side="bottom"}
{: #memory-intel-x86-64b}
{: tab-title="mx2"}
{: tab-group="Memory"}
{: class="simple-tab-table"}
{: summary="Memory mx2 profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | NUMA count | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| mx4-2x16 | 2 / 1 | 1 | 16 | 4 | - |
| mx4d-2x16 | 2 / 1 | 1 | 16 | 4 | 1x65 |
| mx4-4x32 | 4 / 2 | 1 | 32 | 8 | - |
| mx4d-4x32 | 4 / 2 | 1 | 32 | 8 | 1x130 |
| mx4-8x64 | 8 / 4 | 1 | 64 | 16 | - |
| mx4d-8x64 | 8 / 4 | 1 | 64 | 16 | 1x260 |
| mx4-16x128 | 16 / 8 | 1 | 128 | 32 | - |
| mx4d-16x128 | 16 / 8 | 1 | 128 | 32 | 1x520 |
| mx4-24x192 | 24 / 12 | 1 | 192 | 48 | - |
| mx4d-24x192 | 24 / 12 | 1 | 192 | 48 | 1x780 |
| mx4-32x256 | 32 / 16 | 1 | 256 | 64 | - |
| mx4d-32x256 | 32 / 16 | 1 | 256 | 64 | 2x520 |
| mx4-48x384 | 48 / 24 | 1 | 384 | 96 | - |
| mx4d-48x384 | 48 / 24 | 1 | 384 | 96 | 2x780 |
| mx4-64x512| 64 / 32 | 2 | 512 | 128 | - |
| mx4d-64x512| 64 / 32 | 2 | 512 | 128 | 2x780 |
| mx4-96x768| 96 / 48 | 2 | 768 | 192 | - |
| mx4d-96x768| 96 / 48 | 2 | 768 | 192 | 2x780 |
| mx4-128x1024| 128 / 64 | 2 | 1024 | 200 | - |
| mx4d-128x1024| 128 / 64 | 2 | 1024 | 200 | 2x780 |
| mx4-176x1408| 176 / 88 | 2 | 1408 | 200 | - |
| mx4d-176x1408| 176 / 88 | 2 | 1408 | 200 | 2x780 |
{: caption="Memory mx4 profile options for x86-64 instances " caption-side="bottom"}
{: #memory-intel-x86-64-gen4}
{: tab-title="mx4 (Select availability)"}
{: tab-group="Memory"}
{: class="simple-tab-table"}
{: summary="Memory mx4 profile options for Intel x86-64 virtual server instances."}

## Very High Memory
{: #vhmemory}

Very High Memory profiles offer 1 vCPU to 14 GiB of RAM to host small to medium-sized in-memory databases, OLAP services such as SAP NetWeaver, and other memory intensive applications. All Very High Memory profiles are provisioned with temporary SSD-backed [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown) at no additional charge. The following Very High Memory profiles are available on Intel&reg; x86 processors.

The 3rd generation profile with the vx3d prefix is available in the Chennai - Airtel (`in-che`), Mumbai - Airtel (`in-mum`), Toronto (`ca-tor`), and Washington DC (`us-east`) regions to provision virtual server instances on 4th Generation Intel&reg; Xeon&reg; Scalable processors, the Intel 8474C processor (previously code named Sapphire Rapids). For more information about the capabilities of the new profiles, see [Next generation instance profiles](#next-gen-profiles).
{: preview}

- The vx2d profiles are on the Cascade Lake processors.
- The vx3d profiles are on the Sapphire Rapids processors.

| Instance profile | vCPU | Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| vx3d-2x32 | 2 | 1 | 32 | 4 | 1x65 |
| vx3d-4x64| 4 |  2 | 64 | 8 | 1x130 |
| vx3d-8x128 | 8 | 4 | 128 | 16 | 1x260 |
| vx3d-16x256| 16 | 8 | 256 | 32 | 1x520 |
| vx3d-24x384| 24 | 12 | 384 | 48 | 1x780 |
| vx3d-32x512 | 32 | 16 | 512 | 64 | 2x520 |
| vx3d-48x768 | 48 | 24 | 768 | 96 | 2x780 |
| vx3d-64x1024 | 64 | 32 | 1024 | 128 | 2x1024 |
| vx3d-88x1408 | 88 | 44 | 1408 | 176 | 2x1430 |
| vx3d-96x1536 | 96 | 48 | 1536 | 200 | 2x1560 |
| vx3d-128x2048 | 128 | 64 | 2048 | 200 | 2x2080 |
| vx3d-176x2816| 176 | 88 | 2816 | 200 | 2x2860 |
{: caption="Very High Memory profiles options for x86-64 instances" caption-side="bottom"}
{: #vhmemory-intel-x86-64}
{: tab-title="vx3d"}
{: tab-group="Very High Memory"}
{: class="simple-tab-table"}
{: summary="Very High Memory profiles options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU | Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| vx2d-2x28 | 2 | 1 | 28 | 4 | 1x60 |
| vx2d-4x56 | 4 |  2 | 56 | 8 | 1x120 |
| vx2d-8x112 | 8 | 4 | 112 | 16 | 1x240 |
| vx2d-16x224| 16 | 8 | 224 | 32 | 1x480 |
| vx2d-44x616 | 44 | 22 | 616 | 80 | 1x1320 |
| vx2d-88x1232 | 88 | 44 | 1232 | 80 | 2x1320 |
| vx2d-144x2016 | 144 | 72 | 2016 | 80 | 2x2160 |
| vx2d-176x2464 | 176 | 88 | 2464 | 80 | 2x2640 |
{: caption="Very High Memory profiles options for x86-64 instances" caption-side="bottom"}
{: #vhmemory-intel-x86-64b}
{: tab-title="vx2d"}
{: tab-group="Very High Memory"}
{: class="simple-tab-table"}
{: summary="Very High Memory profiles options for Intel x86-64 virtual server instances."}

## Ultra High Memory
{: #uhmemory}

Ultra High Memory profiles are hosted exclusively on the latest generation Intel® Xeon® Platinum Cascade Lake server hosts. This profile family offers our highest vCPU to memory ratio with 28 GiB of memory for every 1 vCPU of compute and up to 5.7 TiB of available RAM and is optimized for running memory intensive applications and in-memory database such as SAP HANA, Memcached, or Redis. All Very High Memory profiles are provisioned with temporary SSD-backed [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown) at no additional charge.

The following Ultra High Memory profiles are available for x86-64 processors:

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|
| ux2d-2x56 | 2 / 1 | 56 | 4 | 1x60 |
| ux2d-4x112 | 4 / 2 | 112 | 8 | 1x120 |
| ux2d-8x224 | 8 / 4 | 224 | 16 | 1x240 |
| ux2d-16x448 | 16 / 8 | 448 | 32 | 1x480 |
| ux2d-36x1008 | 36 / 18 | 1008 | 64 | 1x1080 |
| ux2d-48x1344| 48 / 24 | 1344 | 80 | 2x720 |
| ux2d-72x2016 | 72 / 36 |  2016 | 80 | 2x1080 |
| ux2d-100x2800 | 100 / 50 | 2800 | 80 | 2x1500 |
| ux2d-200x5600 | 200 / 100 | 5600 | 80 | 2x3000 |
{: caption="Ultra High Memory profiles options for x86-64 instances" caption-side="bottom"}
{: #uhmemory-intel-x86-64}
{: tab-title="ux2d"}
{: tab-group="Ultra High Memory"}
{: class="simple-tab-table"}
{: summary="Ultra High Memory profiles options for Intel x86-64 virtual server instances."}

## GPU
{: #gpu}

The GPU and accelerated profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown).

- GPU `-v100` profiles include 1 or 2 NVIDIA V100 PCIe 16 GB GPUs. All OS images are supported on these GPU profiles.
- GPU `-l4` profiles include NVIDIA L4 24 GB GPUs.
- GPU `-l40S` profiles include NVIDIA L40S 48 GB GPUs.
- [Select availability]{: tag-green} GPU `-a100p` profiles include NVIDIA A100 Tensor Core 80 GB GPUs.
- GPU `-h100` profiles include [NVIDIA](https://www.nvidia.com/en-us/data-center/hgx/){: external} GPUs. The system is an HGX design. The H100 offering is available in the following regions and zones: London (eu-gb-2), Sydney (au-syd-2), Toronto (ca-tor-3), Madrid (eu-es-3), Washington DC (us-east-2, us-east-3), Tokyo (jp-tok-3), Sao Paulo (br-sao-1), Dallas (us-south-1), and Frankfurt (eu-de-2).
- [Select availability]{: tag-green} GPU `-h200` profiles include [NVIDIA](https://www.nvidia.com/en-us/data-center/hgx/){: external} GPUs. The system is an HGX design. The H200 offering is available in Washington DC (us-east-2, us-east-3), Toronto (ca-tor-3), Frankfurt (eu-de-2), London (eu-gb-2), Sydney (au-syd-3), and Chennai (in-che-1).
- [Select availability]{: tag-green} GPU `-b300` profiles include [NVIDIA](https://www.nvidia.com/en-us/data-center/hgx/){: external} GPUs. The system is an HGX design. The B300 offering is available in Washington DC (us-east) for select customers. Create a [support case](https://cloud.ibm.com/docs/support?topic=support-open-case&interface=ui&format=markdown) if you are interested in purchasing and using this offering.
- [Select availability]{: tag-green} GPU `-gaudi3` profiles include the [Intel® Gaudi® 3 AI Accelerator](https://www.intel.com/content/www/us/en/products/details/processors/ai-accelerators/gaudi.html). The Intel Gaudi 3 offering is available in Dallas (us-south-dal12-a), Washington DC (us-east-wdc06-a, us-east-wdc07-a), and Frankfurt (eu-de-fra02-a).

Make sure to install the appropriate driver and software for the profile you select:
- [NVIDIA Drivers](https://www.nvidia.com/en-us/drivers/){: external}
- [Intel Gaudi Driver and Software Installation](https://docs.habana.ai/en/latest/Installation_Guide/Driver_Installation.html){: external}

| Instance profile | vCPU / Cores | GiB RAM | Type / Number of GPUs | Bandwidth Cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| gx3-16x80x1l4 | 16 / 8 | 80 | l4 / 1 | 32 | - |
| gx3-32x160x2l4 | 32 / 16 | 160 | l4 / 2 | 64 | - |
| gx3-64x320x4l4 | 64 / 32 | 320 | l4 / 4 | 128 | - |
| gx3-24x120x1l40s | 24 / 12 | 120 | l40s / 1 | 50 | - |
| gx3-48x240x2l40s | 48 / 24 | 240 | l40s / 2  | 100 | - |
| gx3d-24x120x1a100p | 24 / 12 | 120 | a100p / 1  | 48 | 780 |
| gx3d-48x240x2a100p | 48 / 24 | 240 | a100p / 2 | 96 | 1560 |
| gx3d-160x1792x8h100 | 160 / 80 | 1792 | h100 / 8 | 200 | 8x7680 |
| gx3d-160x1792x8h200 | 160 / 80 | 1792 | h200 / 8 | 200 | 8x7680 |
| gx3d-160x1792x8gaudi3 | 160 / 80 | 1792 | Gaudi-3 / 8 | 200 | 8x3200 |
{: caption="GPU gx3 profile options for x86-64 instances" caption-side="bottom"}
{: #gpu-intel-x86-64}
{: tab-title="gx3"}
{: tab-group="GPU"}
{: class="simple-tab-table"}
{: summary="GPU gx3 profile options for x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Type / Number of GPUs | Bandwidth Cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| gx2-8x64x1v100 | 8 / 4 | 64 | v100 / 1 | 16 | - |
| gx2-16x128x1v100 | 16 / 8 | 128 | v100 / 1 | 32 | - |
| gx2-16x128x2v100 | 16 / 8 | 128 | v100 / 2 | 32 | - |
| gx2-32x256x2v100 | 32 / 16 | 256 | v100 / 2 | 64 | - |
{: caption="GPU gx2 16 GB profile options for Intel x86-64 instances" caption-side="bottom"}
{: #gpu-intel-x86-64b}
{: tab-title="gx2"}
{: tab-group="GPU"}
{: class="simple-tab-table"}
{: summary="GPU gx2 16 GB profile options for Intel x86-64 virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Type / Number of GPUs | Bandwidth Cap (Gbps) | Instance storage (GB) |
|---------|---------|---------|---------|---------|---------|
| gx4d-232x3840x8b300 | 232 / 116 | 3840 | b300 / 8 | 200 | 4x7680 |
{: caption="GPU gx4 profile options for x86-64 instances" caption-side="bottom"}
{: #gpu-intel-x86-64c}
{: tab-title="gx4 (Select availability)"}
{: tab-group="GPU"}
{: class="simple-tab-table"}
{: summary="GPU gx4 profile options for x86-64 virtual server instances."}

### Considerations for GPU profiles
{: #considerations-gpu-profiles}

When you create a virtual server by using a GPU or accelerated profile, keep the following recommendations in mind.

- During IBM Cloud periodic maintenance, GPU workloads aren't secure live migrated. Instead, the virtual server instance is restarted. You are notified 30 days in advance of any maintenance where the virtual server instance restarts. For more information, see [Understanding cloud maintenance operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance&format=markdown).
- If you are using GPU profiles, you need to install the required software and drivers onto your virtual server instance. For more information, see [Managing GPUs and accelerators](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-gpus&format=markdown).
- For more information about persistent storage options, see [Storage notes for profiles](#block-storage-notes-for-profiles).
- For GPU profiles that contain instance storage, those block devices are attached as native NVMe drives instead of virtio block devices. The ordering of the instance storage drives regarding storage volumes might differ.

## Storage Optimized
{: #storageopt}

Storage Optimized profiles are hosted exclusively on Intel® Xeon® Platinum Cascade Lake servers. This profile family offers our highest vCPU to [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown) ratio with 300 GB of storage for every 1 vCPU and is optimized for running data lake and other workloads that require more intensive data capabilities. All storage optimized profiles are provisioned with temporary SSD-backed instance storage at no additional charge. For more information, see [Lifecycle of instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown#instance-storage-lifecycle).

Storage Optimized profiles use the `Storage optimized (ox2) instance storage` quota, for instance, storage quota tracking. Unlike other profiles, which use the `Instance storage` quota. For more information, see [Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas&format=markdown#vpcquotas).

The following Storage Optimized profiles are available for x86-64 processors:

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) | Interface type |
|---------|---------|---------|---------|---------|---------|
| ox2-2x16     | 2 / 1 | 16    | 4     | 1x600   | virtio_blk   |
| ox2-4x32     | 4 / 2  | 32    | 8     | 1x1200  | virtio_blk   |
| ox2-8x64     | 8 / 4  | 64    | 16    | 2x1200  | virtio_blk   |
| ox2-16x128   | 16 / 8  | 128   | 32    | 2x2400  | virtio_blk   |
| ox2-32x256   | 32 / 16 | 256   | 64    | 3x3200  | virtio_blk   |
| ox2-64x512   | 64 / 32 | 512   | 80    | 6x3200  | virtio_blk   |
| ox2-96x768   | 96 / 48 | 768   | 80    | 9x3200  | virtio_blk   |
| ox2-128x1024 | 128 / 64 | 1024  | 80    | 12x3200 | virtio_blk   |
{: caption="Storage Optimized profiles options for x86-64 instances" caption-side="bottom"}
{: #storageopt-intel-x86-64}
{: tab-title="ox2"}
{: tab-group="Storage Optimized"}
{: class="simple-tab-table"}
{: summary="Storage Optimized profiles options for Intel x86-64 virtual server instances."}

## Confidential computing profiles
{: #confidential-computing-profiles}

[Select availability]{: tag-green}

Confidential computing with Intel TDX for VPC and confidential computing with Intel SGX for VPC are available in the Dallas (us-south), Washington DC (us-east), and Frankfurt (eu-de) regions.
{: preview}

The following profiles support Intel TDX, Intel SGX, and secure boot. If you prefer to use Intel TDX or Intel SGX without secure boot, you can disable the secure boot option. For more information, see [Secure boot for Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-confidential-computing-with-secure-boot-vpc&format=markdown).

TDX is the default Confidential computing mode for all profiles. Secure boot is enabled by default for all Confidential computing profiles.

All confidential computing profiles support Trusted Domain Extensions (TDX) and secure boot. Profiles with 60 GiB or less memory also support Software Guard Extensions (SGX).

For more information about confidential computing, see [Confidential computing for x86 Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-confidential-computing-vpc&format=markdown).

| Instance profile | vCPU / Cores | GiB RAM | Confidential compute mode  | Bandwidth cap (Gbps) | Instance storage (GB) |
| ---------------- | ---- | ------- | ------------------------- |------- | ------------------------- |
| bx3dc-2x10 | 2 / 1 | 10 | TDX, SGX (4 GB EPC) | 4 | 1x65 |
| bx3dc-4x20 | 4 / 2 | 20 | TDX, SGX (8 GB EPC) | 8 | 1x130 |
| bx3dc-8x40 | 8 / 4 | 40 | TDX, SGX (16 GB EPC) | 16 | 1x260 |
| bx3dc-16x80 | 16 / 8 | 80 | TDX | 32 | 1x520 |
| bx3dc-24x120 | 24 / 12 | 120 | TDX | 48 | 1x780 |
| bx3dc-32x160 | 32 / 16 | 160 | TDX | 64 | 2x520 |
| bx3dc-48x240 | 48 / 24 | 240 | TDX | 96 | 2x780 |
| bx3dc-64x320 | 64 / 32 | 320 | TDX | 128 | 2x1024 |
| bx3dc-96x480 | 96 / 48 | 480 | TDX | 480 | 2x1560 |
{: caption="Balanced profile options for confidential computing compatible virtual server instances" caption-side="bottom"}
{: #balanced-cc-x86-64}
{: tab-title="bx3"}
{: tab-group="Confidential compute"}
{: class="simple-tab-table"}
{: summary="Balanced bx3 profiles for confidential compute compatible virtual server instances."}

| Instance profile | vCPU / Cores | GiB RAM | Confidential compute mode  | Bandwidth cap (Gbps) | Instance storage (GB) |
| ---------------- | ---- | ------- | ------------------------- |------- | ------------------------- |
| cx3dc-2x5 | 2 / 1 | 5 | TDX, SGX (2 GB EPC) | 4 | 1x65 |
| cx3dc-4x10 | 4 / 2 | 10 | TDX, SGX (4 GB EPC) | 8 | 1x130 |
| cx3dc-8x20 | 8 / 4 | 20 | TDX, SGX (8 GB EPC) | 16 | 1x260 |
| cx3dc-16x40 | 16 / 8 | 40 | TDX, SGX (16 GB EPC) | 32 | 1x520 |
| cx3dc-24x60 | 24 / 12 | 60 | TDX, SGX (24 GB EPC) | 48 | 1x780 |
| cx3dc-32x80 | 32 / 16 | 80 | TDX | 64 | 2x520 |
| cx3dc-48x120 | 48 / 24 | 120 | TDX | 96 | 2x780 |
| cx3dc-64x160 | 64 / 32 | 160 | TDX | 128 | 2x1024 |
| cx3dc-96x240 | 96 / 48 | 240 | TDX | 192 | 2x1560 |
| cx3dc-128x320 | 128 / 64 | 320 | TDX | 200 | 2x2860 |
{: caption="Compute profile options for confidential computing compatible virtual server instances" caption-side="bottom"}
{: #compute-cc-x86-64}
{: tab-title="cx3"}
{: tab-group="Confidential compute"}
{: class="simple-tab-table"}
{: summary="Compute cx3 profile options for confidential compute compatible virtual server instances."}

## Flex profiles
{: #flexible-profiles}

Flex profiles are a cost-effective option to help improve mainstream capacity where and when it's needed. Flex offers cpu-to-memory ratio options for compute, balanced, memory, and two low-memory variants (small and nano). The Flex profile family doesn't include instance storage.

The following flex profiles are available.

| Instance profile | vCPU | Memory (GiB) | Bandwidth cap (Gbps)|
|------------------|------|--------------|---------------------|
| nxf-2x1          | 2    | 1            | 2   |
| nxf-2x2          | 2    | 2            | 2   |
| bxf-2x8          | 2    | 8            | 4   |
| bxf-4x16         | 4    | 16           | 8   |
| bxf-8x32         | 8    | 32           | 16  |
| bxf-16x64        | 16   | 64           | 32  |
| bxf-24x96        | 24   | 96           | 48  |
| bxf-32x128       | 32   | 128          | 64  |
| bxf-48x192       | 48   | 192          | 80  |
| bxf-64x256       | 64   | 256          | 80  |
| cxf-2x4          | 2    | 4            | 4   |
| cxf-4x8          | 4    | 8            | 8   |
| cxf-8x16         | 8    | 16           | 16  |
| cxf-16x32        | 16   | 32           | 32  |
| cxf-24x48        | 24   | 48           | 48  |
| cxf-32x64        | 32   | 64           | 64  |
| cxf-48x96        | 48   | 96           | 80  |
| cxf-64x128       | 64   | 128          | 80  |
| mxf-2x16         | 2    | 16           | 4   |
| mxf-4x32         | 4    | 32           | 8   |
| mxf-8x64         | 8    | 64           | 16  |
| mxf-16x128       | 16   | 128          | 32  |
| mxf-24x192       | 24   | 192          | 64  |
| mxf-32x256       | 32   | 256          | 64  |
| mxf-48x384       | 48   | 384          | 80  |
| mxf-64x512       | 64   | 512          | 80  |
{: caption="Flex profile options for virtual servers" caption-side="bottom"}

### Burstable-supported Flex profiles
{: #burstable-supported-flex-profiles}

With supported Flex profiles, you can enable Burstable CPU capability. Burstable means that Flex virtual server CPUs are configured with the baseline CPUs and can "burst" beyond the baseline when idle host CPU capacity is available. For more information, see [Burstable virtual servers](https://cloud.ibm.com/docs/vpc?topic=vpc-burstable-virtual-servers&format=markdown).

The following Burstable profiles are available.

| Name      | vCPU | Memory (GiB) | % vCPU share |
|:----------|:-----|:-------------|:------------|
| nxf-1x1   | 1    | 1            | 10% 25% 50% |
| nxf-1x2   | 1    | 2            | 10% 25% 50% |
| nxf-1x4   | 1    | 4            | 25% 50%     |
| nxf-2x1   | 2    | 1            | 10% 25% 50% |
| nxf-2x2   | 2    | 2            | 10% 25% 50% |
| cxf-2x4   | 2    | 4            | 25% 50%     |
| bxf-2x8   | 2    | 8            | 50%         |
| cxf-4x8   | 4    | 8            | 25% 50%     |
| bxf-4x16  | 4    | 16           |  50%        |
| cxf-8x16  | 8    | 16           | 25% 50%     |
| bxf-8x32  | 8    | 32           |  50%        |
| cxf-16x32 | 16   | 32           | 25% 50%     |
| bxf-16x64 | 16   | 64           |  50%        |
{: caption="Burstable-supported Flex profile options for virtual servers" caption-side="bottom"}

## High Frequency profiles
{: #high-frequency-profiles}

High Frequency profiles provide CPUs with a high frequency, which generally enables higher performance per core than other profiles that are within the same hardware generation. The high frequency profile provides AMD&reg; 5th Generation Epyc 9575F processor-based virtual server instances. This processor offers all-core boost speeds up to 4.5 HZ and a max turbo speed of 5 GHz. AMD 5th Generation Epyc 9575F uses Chiplet-based architecture with distributed L3 cache. Distributed L3 cache can ensure that more dedicated L3 is shared per CPU. High Frequency profiles support pooled bandwidth allocation for data volumes. For more information, see [Volume bandwidth allocation method](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-bandwidth&format=markdown#attached-block-vol-bandwidth).

The Gen 4 High Frequency 1.4 TB RAM hx4da profiles are available only in the Dallas (us-south) region. All other hx4a and hx4da profiles are available in both the Dallas (us-south) and Sydney (au-syd) regions. All profiles have the AMD 5th Generation Epyc 9575F processor-base to provision virtual server instances. For more information about the capabilities of the new profile, see [High Frequency profiles - Gen 4](https://cloud.ibm.com/docs/vpc?topic=vpc-high-frequency-profile-family&format=markdown).
{: preview}

The following table lists available AMD hx4da and hx4a profiles.

| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) | NUMA Count |
| ---------------- | ---- | ------- | ------- | ------- | ---- |
| hx4da-16x32 |	16 / 8 | 32 |	32 | 520 | - |
| hx4da-16x64 |	16 / 8 | 64 |	32 |	520 | - |
| hx4da-16x128 | 16 / 8 |	128 |	32 | 520 | - |
| hx4da-64x680 | 32/64 | 680 | 200 | 2600 | 2 |
| hx4da-128x680 | 64/128 | 680 | 200 | 2600 |	2 |
| hx4da-192x680 |	96/192 | 680 | 200 | 2600 | 2 |
| hx4da-248x680 | 248 / 124 | 680 | 200 | 1x2600 | 2 |
| hx4da-64x1408	| 32/64	| 1408 | 200 | 2600 | 2 |
| hx4da-128x1408 | 64/128 |	1408 | 200 | 2600 | 2 |
| hx4da-192x1408 | 96/192 |	1408 | 200 | 2600 | 2 |
| hx4da-248x1408 | 124/248 | 1408 | 200 | 2600 | 2 |
{: class="simple-tab-table"}
{: caption="High Frequency profiles (hx4da) for compatible virtual server instances" caption-side="bottom"}
{: tab-group="high-frequency-profiles"}
{: #hx4da-profiles}
{: tab-title="hx4da"}


| Instance profile | vCPU / Cores | GiB RAM | Bandwidth cap (Gbps) | Instance storage (GB) | NUMA Count |
| ---------------- | ---- | ------- | ------- | ------- | ---- |
| hx4a-8x16 | 8 / 4 | 16 | 16 |	 - | - |
| hx4a-8x32 |	8 / 4 |	32 |	16 |  - | - |
| hx4a-8x64 |	8 / 4 |	64 |	16 | - | - |
| hx4a-8x128 | 8 / 4 | 128 |	16 | - | - |
| hx4a-16x32 | 16 / 8 |	32 |	32 | - | - |
| hx4a-16x64 | 16 / 8 |	64 | 32 | - | - |
| hx4a-16x128	| 16 / 8 | 128 |	32 | - | - |
{: class="simple-tab-table"}
{: caption="High Frequency profiles (hx4a) for compatible virtual server instances" caption-side="bottom"}
{: tab-group="high-frequency-profiles"}
{: #hx4a-profiles}
{: tab-title="hx4a"}

## Bandwidth allocation
{: #bandwidth-allocation}

Instance bandwidth is allocated between volume bandwidth and networking bandwidth. The bandwidth capacity (Bandwidth Cap) is determined by the virtual server profile that you select during instance provisioning. For example, a bx2-2x8 balanced server profile allows a bandwidth cap of 4 Gbps.

### Bandwidth allocation between storage and networking
{: #bandwidth-storage-network}

The initial volume and network bandwidth allocation depends on the bandwidth that is set by the instance profile that you selected. You can also see the bandwidth allocations in the profile information during instance creation in the console. The bandwidth allocation between Storage and Network can be changed on the instance details page after you provision an instance.

For example, for the bx2-2x8 profile, you might have the following bandwidth configuration:

- Storage: 1 Gbps
- Network: 3 Gbps

You can adjust the amount of overall bandwidth that is provided to storage volumes within the overall instance limits. However, both volume and network bandwidth must be at least 500 MBps each. For example, to allow more bandwidth for volumes, you can apportion the bx2-2x8 example in equal allocations:
   - Storage: 2 Gbps
   - Network: 2 Gbps

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles&format=markdown) and [Adjusting bandwidth allocation by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=ui&format=markdown#adjusting-bandwidth-allocation-ui).
{: ui}

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles&format=markdown) and [Adjusting bandwidth allocation by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=cli&format=markdown#adjusting-bandwidth-allocation-cli).
{: cli}

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles&format=markdown) and [Adjusting total storage bandwidth allocation from the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=api&format=markdown#adjusting-bandwidth-allocation-api).
{: api}

### Bandwidth allocation with multiple data volumes
{: #bandwidth-multi-volumes}

By default, the storage bandwidth is divided between all attached volumes. To help ensure reasonable boot times, a minimum of 393 MBps is allocated to the primary boot volume. The remaining volume bandwidth can be divided between the attached data volumes proportionally (weighted bandwidth allocation) or shared between the attached data volumes (pooled bandwidth allocation).

When weighted bandwidth allocation is used, the data volumes are assigned bandwidth that is proportional to their maximum bandwidth. The weights are based on the size, IOPS, and bandwidth values of the storage volumes. Each volume can use only the bandwidth that is assigned to it at the time of attachment.

Review the [compute profiles details](https://cloud.ibm.com/docs/vpc?group=profile-details&format=markdown) to see the volume bandwidth allocation capabilities available. For more information about the bandwidth allocation, see the [Bandwidth allocation for Data Volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-bandwidth&interface=ui&format=markdown#attached-block-vol-bandwidth).

### Bandwidth allocation with multiple network interfaces
{: #bandwidth-multi-vnic}

You can add up to 15 network interfaces for your virtual server instance, depending on the vCPU count that is included in the instance profile.

* 2-16 vCPUs: Up to five network interfaces
* 17-48 vCPUs: Up to 10 network interfaces
* 49 or more vCPUs: Up to 15 network interfaces

With [flex profiles](#flexible-profiles), you can add up to 2 network interfaces for a virtual server instance, depending on the vCPU count that is included in the profile.

* 2-4 vCPUs: 1 network interface
* 8 or more vCPUs: 2 network interfaces

With multiple network interfaces, bandwidth is distributed evenly across the network interfaces that are attached to the virtual server instance.

For more information, see [Managing network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnics&format=markdown).

## Block Storage volume notes for profiles
{: #block-storage-notes-for-profiles}

When you create the data volumes, you can select a volume profile that best meets your requirements. The second-generation volume profile, `sdp` provides the most flexibility, as you can specify your capacity, IOPS, and throughput maximum values. For more information, see the [SSD defined performance profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#defined-performance-profile). First-generation volume profiles are available as three predefined [tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#tiers) or as a [custom profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#custom). These volume profiles relate to virtual server instance profiles:

- A [3 IOPS general-purpose tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#tiers) provides IOPS/GB performance that is suitable for a virtual server instance Balanced profile.
- A [5-IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#tiers) profile provides IOPS/GB performance that is suitable for a virtual server instance Compute profile.
- A [10-IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&format=markdown#tiers) profile provides IOPS/GB performance that is suitable for a virtual server instance Memory profile.

## Understanding profile naming
{: #profiles-naming-rule}

The following information describes the profile naming rules.

The first character represents the profile families. Different profile families have different ratios of vCPU to memory and other characteristics that are designed for different workloads.

- "n" nano family of profiles
- "b": balanced family of profiles
- "c": compute family of profiles (higher on the CPUs)
- "m": memory family of profiles (higher on the memory)
- "u": ultra high memory family of profiles, 1 vCPU to 28 GiB of memory ratio
- "v": very high memory family of profiles, 1 vCPU to 14 GiB of memory ratio
- "g": GPU profiles, which is a 1:8 or 1:16 ratio
- "o": storage optimized family of profiles, 1 vCPU to 8 GiB memory ratio and 1 vCPU to 300 GB instance storage ratio
- "f": flex profiles offer a broad set of capabilities and scale from 2 vCPUs (1 physical core) up to 64 vCPUs (64 physical cores).
- "h": high frequency family of profiles

The second character represents the CPU architecture.

- "x": x86_64
- [Deprecated]{: tag-deprecated} "z": s390x

The third character represents the generation of the IBM Cloud infrastructure where the profile is provisioned, such as a "2" or "3". A value of "f" indicates that the profile is flexible and can provision on any infrastructure generation.

If the fourth character is a "d", such as bx3d, then a defined quantity of instance storage is provisioned with the virtual server.
If the last character is a "c", such as bx3c or bx3dc, then the profile supports confidential computing.

The characters after "-" represents the number of vCPUs and the size of RAM (GiB). For example, "2x4" means that this profile has 2 vCPU and 4 GiB of RAM.

Using “bx2-4x16” as an example, you can know from the name that it is a balanced profile that provides 4 vCPUs of compute and 16 GiB of memory. The profile is deployed on an x86-based host and is for the second-generation VPC.

## Viewing profile configurations
{: #popular-profiles}

You can view available profile configurations by using the IBM Cloud console, CLI, or the API. In the IBM Cloud console, you can select from popular profile configurations that support the most common use cases.

### Viewing instance profiles in the console
{: #profiles-using-console}
{: ui}

1. In the IBM Cloud console, click the **Navigation Menu** icon ![menu icon](../../icons/icon_hamburger.svg) **> Infrastructure** ![VPC icon](../../icons/vpc.svg) **> Compute > Virtual server instances**.
2. From the Virtual server instances page, click **New instance**.
3. You can either select a profile configuration from **Popular profiles** or click **All profiles** to view more configurations.

### Viewing instance profiles from the CLI
{: #profiles-using-cli}
{: cli}

To view the list of available instance profiles by using the CLI, run the following command:

```sh
ibmcloud is instance-profiles
```
{: pre}

### Viewing instance profiles with the API
{: #profiles-using-api}
{: api}

To view the list of available instance profiles by using the API, you can call the [List all instance profiles API](https://cloud.ibm.com/docs/apis/vpc#list-instance-profiles).

The following request example lists the available instance profiles. When you call the API, replace the API endpoint and IAM token with the values from your enterprise. For more information about the `$vpc_api_endpoint` and `$iam_token` variables, see the Authentication and Endpoint URLs sections in [Virtual Private Cloud API Introduction](https://cloud.ibm.com/docs/apis/vpc/latest#about-vpc-api).

```sh
curl -X GET \
"$vpc_api_endpoint/v1/instance/profiles?version=2021-02-23&generation=2" \
-H "Authorization: Bearer $iam_token"
```
{: codeblock}

## Next generation instance profiles
{: #next-gen-profiles}

The 3rd generation of IBM Cloud Virtual Servers for VPC are available to provision in all regions. This new generation features virtual server profile families that are hosted exclusively on Intel 4th Generation Xeon Scalable processors to provide the most powerful and performant general-purpose profiles available. These 3rd generation profiles provide the following enhancements:

- Improved performance with DDR 5 memory DIMMs, PCI Gen 5 interconnects, and more memory per vCPU than prior generation profiles.
- A wide variety of profiles sizes with core to memory ratios optimized to maximize performance and economics for intensive workloads.
- Enhanced integrated accelerators that feature AMX-512, AVX, and enhanced crypto acceleration.
- Instances are started by default with Open Virtual Machine Format (OVMF), and run in Unified Extensible Firmware Interface (UEFI) mode for enhanced security.
- Local instance storage is included with all profiles for ease of access to temporary storage and swap space. For more information about the temporary nature of instance storage, see [Lifecycle of instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage&format=markdown#instance-storage-lifecycle).
- Optional dynamic bandwidth allocation for volume attachments.
- A 3rd generation profile can be resized to a 2nd generation profile. A 2nd generation profile can be resized to a 3rd generation profile. For more information, see [Resizing between Gen 2 and Gen 3 profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance&interface=ui&format=markdown#resizing-instance-generations).

## Intel Hyper-Threading Technology
{: #vpc-intel-hyper-threading-technology}

All Intel&reg; x86-64 servers have Hyper-Threading enabled by default. Intel&reg; Hyper-Threading Technology is a term that describes simultaneous multithreading (SMT). Hyper-Threading Technology splits each physical core into two virtual processors. Hyper-Threading Technology is like taking a wide road with a single lane and making it into two relatively narrower lanes. The two-lane highway provides better service over the single-lane road if traffic is moving slow and fast. Hyper-Threading Technology provides better application performance for File I/O, Network I/O, and other slower operations mixed with CPU-intensive operations. The performance advantage of Hyper-Threading Technology typically ranges in the range 0 - 30% over a single-thread mode. Some applications might also see a drop in performance.

If you want to disable Intel&reg; Hyper-Threading, see [Disabling Intel Hyper-Threading Technology](https://cloud.ibm.com/docs/vpc?topic=vpc-disabling-hyper-threading&format=markdown).

## Next steps
{: #nextsteps-profiles}

After you choose a profile, you're ready to create an instance.

- [Creating an instance by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=ui&format=markdown#creating-virtual-servers-ui)
- [Creating an instance by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli&format=markdown#creating-virtual-servers-cli)
- [Creating an instance by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=api&format=markdown)
- [Creating an instance by using Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=terraform&format=markdown#create-instance-terraform)
- [Managing GPUs](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-gpus&format=markdown)