General Computing-Basic ECSs
General Computing-Basic T6
Overview
General computing-basic ECSs are suitable for scenarios that require moderate CPU performance generally but burstable high performance occasionally while keeping costs low. The performance of such ECSs is constrained by the baseline performance and CPU credits.
Hyper-threading is enabled for this type of ECSs by default. Each vCPU is a thread of a CPU core.
- Before using general computing-basic ECSs, learn about the concepts related to CPU credits by referring to CPU Credits of T6 ECSs.
- CPU credits do not incur additional costs. For more information about CPU credits, see CPU Credits.
Series |
Compute |
Disk Type |
Network |
---|---|---|---|
T6 |
|
|
|
Notes
General computing-basic T6 ECSs are suitable for scenarios that require moderate CPU performance generally but burstable high performance occasionally. The performance of such ECSs is constrained by the baseline performance and CPU credits. After a T6 ECS is created, you can view its CPU credits by choosing More > Manage Credits in the Operation column.
Scenarios
General computing-basic ECSs are suitable for applications that require moderate CPU performance generally but burstable high performance occasionally, such as web application servers, light-load applications, and microservices.
Specifications
Flavor |
vCPUs |
Memory (GiB) |
CPU Baseline (%) |
Average CPU Baseline (%) |
Max./Assured Bandwidth (Gbit/s) |
Max. PPS (10,000) |
Network Connections (10,000) |
Max. NIC Queues |
Max. NICs |
Virtualization |
---|---|---|---|---|---|---|---|---|---|---|
t6.small.1 |
1 |
1 |
10 |
10 |
0.3/0.05 |
6 |
30 |
1 |
1 |
KVM |
t6.large.1 |
2 |
2 |
40 |
20 |
0.5/0.1 |
10 |
30 |
1 |
1 |
KVM |
t6.xlarge.1 |
4 |
4 |
80 |
20 |
1/0.2 |
20 |
30 |
2 |
2 |
KVM |
t6.2xlarge.1 |
8 |
8 |
120 |
15 |
2/0.4 |
40 |
30 |
4 |
2 |
KVM |
t6.4xlarge.1 |
16 |
16 |
240 |
15 |
3/0.8 |
60 |
50 |
8 |
2 |
KVM |
t6.medium.2 |
1 |
2 |
10 |
10 |
0.3/0.05 |
6 |
30 |
1 |
1 |
KVM |
t6.large.2 |
2 |
4 |
40 |
20 |
0.5/0.1 |
10 |
30 |
1 |
1 |
KVM |
t6.xlarge.2 |
4 |
8 |
80 |
20 |
1/0.2 |
20 |
30 |
2 |
2 |
KVM |
t6.2xlarge.2 |
8 |
16 |
120 |
15 |
2/0.4 |
40 |
30 |
4 |
2 |
KVM |
t6.4xlarge.2 |
16 |
32 |
240 |
15 |
3/0.8 |
60 |
50 |
8 |
2 |
KVM |
t6.large.4 |
2 |
8 |
40 |
20 |
0.5/0.1 |
10 |
30 |
1 |
1 |
KVM |
t6.xlarge.4 |
4 |
16 |
80 |
20 |
1/0.2 |
20 |
30 |
2 |
2 |
KVM |
t6.2xlarge.4 |
8 |
32 |
120 |
15 |
2/0.4 |
40 |
30 |
4 |
2 |
KVM |
CPU Credits of T6 ECSs
- Initial CPU credits: After a T6 ECS is created, it automatically obtains initial CPU credits. Initial CPU credits are allocated only after an ECS is created.
For example, after a t6.large.1 ECS is created, it obtains 60 initial CPU credits.
- Maximum CPU credits: If the CPU usage is below the baseline, credits earned (accrued credits) are greater than credits spent. The accrued credits will not expire on a running ECS. When the credits reach the maximum value allowed (depending on the ECS flavor), no more credits will be earned.
For example, the maximum number of CPU credits for a t6.large.1 ECS is 576. When the credits reach 576, no more credits will be earned. When the credits are below 576, credits can be earned again.
- CPU credits earned per hour: The number of CPU credits earned by an ECS per hour reflects the CPU baseline. One CPU credit is equal to one vCPU running at 100% usage for one minute.
For example, a t6.large.1 ECS can earn 24 CPU credits per hour.
Flavor |
Initial CPU Credits |
Maximum CPU Credits |
CPU Credits Earned per Hour |
---|---|---|---|
t6.small.1 |
30 |
144 |
6 |
t6.large.1 |
60 |
576 |
24 |
t6.xlarge.1 |
120 |
1,152 |
48 |
t6.2xlarge.1 |
120 |
1,728 |
72 |
t6.4xlarge.1 |
160 |
3,456 |
144 |
t6.medium.2 |
30 |
144 |
6 |
t6.large.2 |
60 |
576 |
24 |
t6.xlarge.2 |
120 |
1,152 |
48 |
t6.2xlarge.2 |
120 |
1,728 |
72 |
t6.4xlarge.2 |
160 |
3,456 |
144 |
t6.large.4 |
60 |
576 |
24 |
t6.xlarge.4 |
120 |
1,152 |
48 |
t6.2xlarge.4 |
120 |
1,728 |
72 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot