Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

ECS Types

Updated on 2025-01-26 GMT+08:00
The cloud platform provides the following ECS types for different application scenarios:

x86 and Kunpeng Architectures

ECS supports the following architectures:

  • x86 architecture

    The x86 architecture uses the complex Instruction Set Computer (CISC). CISC has a large collection of complex instructions that range from simple to very complex and specialized in the assembly language level, which takes a long time to execute the instructions.

  • Kunpeng architecture

    The Kunpeng architecture uses the reduced Instruction Set Computer (RISC). RISC a microprocessor architecture with a simple collection and highly customized set of instructions. It is built to minimize the instruction execution time by optimizing and limiting the number of instructions.

    The Kunpeng architecture delivers more balanced performance/power consumption than the x86 architecture.

Table 1 Comparison between the x86 and Kunpeng architectures

Dimension

x86 Architecture

Kunpeng Architecture

Advantage

Good ecosystem, support for almost all general software

Huawei-developed processors, cost-effective

Scenario

Platform-dependent scenarios using Windows software and x86-compatible commercial software

  • Platform-independent scenarios such as e-commerce, big data, and scientific computing
  • Native scenarios such as mobile phone simulation

ECS Flavor Naming Rules

Figure 1 shows a flavor name, which consists of the instance family and generation, instance size, and memory/vCPU ratio.

Figure 1 Flavor naming rule
NOTE:

Certain flavor names contain additional identifiers. For example, c6h.22xlarge.2.physical contains the additional identifier physical, which indicates that this instance is a bare metal ECS.

  • Instance types

    The instance type is named in the following format: CPU architecture + instance family + instance generation + additional capabilities.

    Table 2 describes the naming rule for the instance type.
    Table 2 Naming rule for the instance type

    Item

    Description

    Rule

    Example

    Processor family

    Indicates the CPU architecture.

    Represented in a lowercase letter.

    • x86: There is no prefix by default.
    • Kunpeng: The prefix is a lowercase letter k.

    Instance family

    Indicates the typical scenarios.

    Represented in a lowercase letter.

    See Table 3.

    Instance generation

    Indicates the evolution of the instance family.

    Represented in a digit. The digit increases as the hardware and architecture evolves.

    None

    Additional capabilities

    Indicate the enhanced capabilities of the instance when compared with the other instances of the same generation.

    Represented in lowercase letters.

    See Table 4.

    Table 3 Instance families

    Application Scenarios

    Segmented Scenarios

    Instance Family

    Description

    General-purpose

    General Computing-Basic

    t

    Turbo

    General Computing

    s

    Standard

    General Computing-plus

    c

    Compute

    High-performance computing

    High-Performance Computing

    h

    High Performance

    Big data

    Disk-intensive

    d

    Disk

    Ultra-high I/O (large-capacity local disks)

    i

    IOPS

    Ultra-high I/O (small-capacity local disks)

    ir

    IOPS Raid

    Memory-intensive

    Memory-optimized

    m

    Memory

    Large-Memory

    e

    Enhanced Memory

    Computing-accelerated

    GPU computing-accelerated

    p

    Parallel

    GPU graphics-accelerated

    g

    Graphic

    GPU inference-accelerated

    pi

    Parallel Inference

    FPGA-accelerated

    fp

    FPGA Performance

    AI inference-accelerated

    ai

    Ascend Inference

    Table 4 Additional capabilities

    Suffix

    Example

    Description

    ne

    c3ne

    Network Enhanced

    s

    c6s

    Standard

    v

    p2v

    NVlink

    h

    c6h

    High performance

  • Instance sizes

    The instance sizes can be small, medium, large, xlarge, or Nxlarge, as shown in Table 5.

    For example, 2xlarge in s6.2xlarge.4 indicates that there are 8 vCPUs.
    Table 5 Mapping between instance size and the number of vCPUs

    Instance Size

    vCPUs

    small

    1

    medium

    1

    large

    2

    xlarge

    4

    Nxlarge

    N × 4. A larger value of N indicates more vCPUs.

  • Memory/vCPU ratio

    It is represented by a digit.

    For example, 4 in s6.2xlarge.4 indicates a memory-to-vCPU ratio of 4, which means that there are 8 vCPUs and the memory size is 32 GiB.

  • Additional identifies

    The bare metal ECSs that share a resource pool with BMSs are identified by physical.

    For example, physical in c6h.22xlarge.2.physical indicates a bare metal ECS that shares a resource pool with BMSs.

vCPU

ECS supports hyper-threading, which enables two threads to run concurrently on a single CPU core. Each thread is represented as a virtual CPU (vCPU) and a CPU core contains two vCPUs (logical cores).

Hyper-threading is enabled for most ECS flavors by default. If hyper-threading is disabled during the ECS creation or flavor change, the number of vCPUs queried from the ECS is half of the number of vCPUs defined by the ECS flavor.

For example, a 2-core physical CPU contains 4 vCPUs (threads).

Network QoS

Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.

To obtain the QoS data of an ECS flavor, including the maximum/assured bandwidth, maximum intranet PPS, NIC multi-queues, and maximum NICs, see A Summary List of x86 ECS Specifications.

Constraints on network performance vary depending on ECS flavors.
  • Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when there is a network bandwidth contention in the entire network.
  • Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).
  • Maximum intranet PPS: indicates the maximum ECS capability in sending and receiving packets.

    PPS: packets per second, indicates the number of packets received and sent per second. It is usually used to measure the network performance.

  • NIC multi-queues: allocates NIC interruptions to multiple vCPUs for higher PPS performance and bandwidth
  • Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.
  • Maximum supplementary NICs: indicates the maximum number of supplementary NICs that can be attached to an ECS.
  • IPv6: indicates whether ECSs support IPv6 addresses.

    The ECS flavors supporting IPv6 addresses vary depending on the regions and AZs. Whether an ECS flavor supports IPv6 addresses is displayed on the console after a region and an AZ are selected.

    Figure 2 Checking whether an ECS flavor supports IPv6
NOTE:
  • For instructions about how to test packet transmit and receive, see How Can I Test Network Performance?
  • For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
  • The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
  • A NIC refers to an elastic network interface. You can create and configure network interfaces and attach them to your ECSs for flexible and highly available network configurations.

    For details, see Elastic Network Interface.

  • A supplementary NIC is a supplement to NICs. If the number of NICs that can be attached to your ECSs cannot meet your requirements, you can use supplementary NICs.

    For details, see Supplementary Network Interface.

Dedicated and Shared ECSs

Table 6 Differences between dedicated and shared ECSs

Dimension

Dedicated ECS

Shared ECS

CPU Allocation

CPUs are exclusively used and there is no CPU contention.

CPUs are shared and CPU contention may occur.

Feature

  • High performance
  • Dedicated and stable computing, storage, and network resources
  • High costs
  • Unstable performance when loads are high
  • Shared computing, storage, and network resources
  • Low costs

Application Scenario

For enterprises that have high requirements on service stability

For small- and medium-sized websites or individuals that have requirements on cost-effectiveness

ECS Specifications

Specifications except general computing and general computing-basic

x86 computing:

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback