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-27 GMT+08:00
The cloud platform provides the following ECS types for different application scenarios:

ECS Flavor Naming Rules

ECS flavors are named in the "AB.C.D" format.

Example: s2.medium.4

Figure 1 ECS flavor naming rules

The format is defined as follows:

  • AB indicates the ECS type and type ID.
    • A specifies the ECS type. For example, s indicates a general-computing ECS, c indicates a general computing-plus ECS, and m indicates a memory-optimized ECS.
    • B specifies the type ID. For example, 1 in s1 indicates the first-generation general-computing ECS, and 2 in s2 indicates the second-generation general-computing ECS. Generally, a larger number indicates a newer generation, which is more cost-effective. For example, compared with s1 and s2, s6 is more cost-effective.
  • C specifies the flavor size (the number of vCPUs), such as small, medium, large, xlarge, 2xlarge, 4xlarge, and 8xlarge.
  • D specifies the ratio of memory to vCPUs and is expressed in a digit. For example, value 4 indicates that the ratio of memory to vCPUs is 4.
    Table 1 Mapping between flavor and the number of vCPUs

    Flavor Size

    vCPUs

    small

    1

    medium

    1

    large

    2

    xlarge

    4

    Nxlarge

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

How Do I Know My ECS Flavor?

When creating an ECS, you can view the flavors in the flavor list.

Figure 2 ECS flavors

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 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.
NOTE:
  • For instructions about how to test packet transmit and receive, see How Can I Test the Network Performance of Linux ECSs?
  • 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.

Dedicated and Shared ECSs

Table 2 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-purpose

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