edit-icon download-icon

How to use guaranteed-performance instances?

Last Updated: Apr 09, 2018

1. What are guaranteed-performance instances?

2. How are guaranteed-performance instances charged?

3. What is the price of each capacity?

4. How to choose capacities for guaranteed-performance instances?

5. Can I modify the capacity after the instance is created?

6. When will Alibaba Cloud start to charge guaranteed-performance instances?

7. After Alibaba Cloud starts to charge capacity fee on guaranteed-performance instances, will it charge additional fees on shared-performance instances?

8. Why sometimes guaranteed-performance instances cannot reach the performance limit defined in the capacity?

9. Why sometimes the performance of a low-capacity guaranteed-performance instance is worse than that of a shared-performance instance?

10. Can I still buy shared-performance instances?

11. Will intranet SLB instances be charged for capacity fee?

1. What are guaranteed-performance instances?

A guaranteed-performance instance provides guaranteed performance metrics (performance SLA) and is opposite to a shared-performance instance. For a shared-performance instance, the performance metrics are not guaranteed and the resources are shared by all instances.

All instances are shared-performance instances before Alibaba launches guaranteed-performance instances. You can view the instance type on the console. Hover your mouse pointer to the green icon of the target instance to view the performance metrics, as shown in the following figure.

slb

The following are three key performance metrics for guaranteed-performance instances:

  • Max Connection

    The maximum number of connections to a SLB instance. When the maximum number of connections reaches the limits of the capacity, the new connection will be dropped.

  • Connection Per Second (CPS)

    The rate at which a new connection is established per second. When the CPS reaches the limits of the capacity, the new connection will be dropped.

  • Query Per Second (QPS)

    The number of HTTP/HTTPS requests that can be processed per second. When the QPS reaches the limits of the capacity, the new connection will be dropped.

    This metrics is only available for Layer-7 Server Load Balancer.

Alibaba Cloud Server Load Balancer provides the following capacities for guaranteed-performance instances:

Note: If you want to use a larger capacity, contact your customer manager.

CapacityMax ConnectionCPSQPS
Capacity 1 Small I (slb.s1.small) 5,000 3,000 1,000
Capacity 2 Standard I (slb.s2.small) 50,000 5,000 5,000
Capacity 3 Standard II (slb.s2.medium) 100,000 10,000 10,000
Capacity 4 Higher I (slb.s3.small) 200,000 20,000 20,000
Capacity 5 Higher II (slb.s3.medium) 500,000 50,000 30,000
Capacity 6 Super I (slb.s3.large) 1,000,000 100,000 50,000

2. How are guaranteed-performance instances billed?

Guaranteed-performance instances are billed as follows:

Total fee (per instance) = instance fee + traffic fee + capacity fee

The corresponding capacity fee is billed for each guaranteed-performance instance no matter the network type of the instance, and is billed based on the actual usage depending on the capacity selected. If the actual performance metrics of an instance occurs between two capacities, the capacity fee is charged at the higher capacity fee. For more information about the SLB billing, see Billing.

The corresponding capacity fee is billed for each guaranteed-performance instance no matter the network type of the instance, and is billed based on the actual usage depending on the capacity selected. If the actual performance metrics of an instance occurs between two capacities, the capacity fee is charged at the higher capacity fee.

For example, if you purchase the Super I (slb.s3.large) capacity, and the actual usage of your instance in an hour is as follow:

Max ConnectionCPSQPS
90,0004,00011,000

  • From the perspective of Max Connection, the actual metrics 90,000 occurs between the limit 50,000 defined in the Standard I (slb.s2.small) capacity and the limit 100,000 defined in the Standard II (slb.s2.medium) capacity. Therefore, the capacity of the Max Connection metrics in this hour is Standard II (slb.s2.medium).

  • From the perspective of CPS, the actual metrics 4,000 occurs between the limit 3,000 defined in the Small I (slb.s1.small) capacity and the limit 5,000 defined in the Standard I (slb.s2.small) capacity. Therefore, the capacity of the CPS metrics in this hour is Standard I (slb.s2.small).

  • From the perspective of QPS, the actual metrics 11,000 occurs between the limit 10,000 defined in the Standard II (slb.s2.medium) capacity and the limit 20,000 defined in the Higher I (slb.s3.small) capacity. Therefore, the capacity of the QPS metrics in this hour is Higher I (slb.s3.small)

    Comparing these three metrics, the capacity of the QPS metrics is highest, therefore, the capacity fee of the instance in this hour is charged at the price of the Higher I (slb.s3.small) capacity.

The following figure is an example showing how the capacity fee is billed for an SLB instance in the first three hours:

SLB

The billing of the guaranteed-performance instances is flexible. The performance capacity selected when purchasing an SLB instance limits the performance. For example, if slb.s3.medium is selected, the new connections are dropped when the HTTP requests in one second reach 30,000.

3. What is the price of each capacity?

The following table lists the capacity price of each capacity. For the price on the SLB instance and traffic, see Billing.

RegionsCapacityMax ConnectionCPS QPSUSD/Hour

China North 2 (Beijing)

China North 3 (Zhangjiakou)

China North 5 (Huhehaote)

China North 1 (Qingdao)

China North 2 (Beijing)

China East 2 (Shanghai)

China South 1 (Shenzhen)

Capacity 1 Small I (slb.s1.small) 5000 3000 1000 Free of charge
Capacity 2 Standard I (slb.s2.small) 50000 5000 5000 0.05
Capacity 3 Standard II (slb.s2.medium) 100000 10000 10000 0.10
Capacity 4 Higher I (slb.s3.small) 200000 20000 20000 0.20
Capacity 5 Higher II (slb.s3.medium) 500000 50000 30000 0.31
Capacity 6 Super I (slb.s3.large) 1000000 100000 50000 0.51

Asia Pacific SE 1 (Singapore)

Asia Pacific SE 3 (Kuala Lumpur)

Asia Pacific SE 5 (Jakarta)

Asia Pacific SOU 1 (Mumbai)

US West 1 (Silicon Valley)

US East 1 (Virginia)

Hong Kong

Capacity 1 Small I (slb.s1.small) 5000 3000 1000 Free of charge
Capacity 2 Standard I (slb.s2.small) 50000 5000 5000 0.06
Capacity 3 Standard II (slb.s2.medium) 100000 10000 10000 0.12
Capacity 4 Higher I (slb.s3.small) 200000 20000 20000 0.24
Capacity 5 Higher II (slb.s3.medium) 500000 50000 30000 0.37
Capacity 6 Super I (slb.s3.large) 1000000 100000 50000 0.61

Capacity fees of guaranteed-performance instances in the international regions can enjoy an 83% discount.

4. How to select a capacity?

Because the capacity fee is billed based on the actual usage, we recommend that you select the largest capacity (slb.s3.large). This guarantees the business flexibility (flexibility) and will not cause extra costs. If your traffic does not reach the largest capacity, you can select a more reasonable capacity, such as slb.s3.medium.

5. Can I modify the capacity after the instance is created?

Yes.

You can change the capacity at any time and the change takes effect immediately. For more information, see Change the configuration.

Note:

  • After you change a shared-performance instance to a guaranteed-performance instance, you cannot change it back.

  • If you change a shared-performance instance to a guaranteed-performance instance, a brief disconnection of service may occur for 10 to 30 seconds.

  • The IP of the SLB instance will not be changed after you changing the instance type or the capacity.

6. When will be the guaranteed-performance instances charged?

Alibaba Cloud launched the guaranteed-performance instances in May 2017, and will charge the capacity fee on guaranteed-performance instances from April 1, 2018.

Pay attention to official announcement, messages, and emails for notification.

7. After Alibaba Cloud starts to charge capacity fee on guaranteed-performance instances, will extra fees be charged on shared-performance instances?

No.

The billing of the original shared-performance instances is the same if you do not change it to a performance-guaranteed instance. However, if you change the shared-performance instance to the guaranteed-performance one, the capacity fee will be charged from April 1st, 2018.

8. Why sometimes guaranteed-performance instances cannot reach the performance limit as defined in the capacity?

It applies to the cask theory.

Guaranteed-performance instances do not guarantee that the three metrics can reach the capacity limits at the same time. The limitation is triggered as long as a metric first reaches the limitation defined in the capacity.

For example, you have purchased a guaranteed-performance instance of the Higher I (slb.s3.small) capacity. When the QPS of the instance reaches 20,000 but the number of maximum connections does not reach 200,000, the new connections are still dropped because the QPS has reached the limitation.

9. Why sometimes the performance of a smaller capacity guaranteed-performance instance is less efficient than that of a shared-performance instance?

For a shared-performance instance, all the resources are shared. Its performance cannot be guaranteed when the traffic load is high. However, a guaranteed-performance instance can guarantee the performance at any time. Because the capacity fee is billed based on the actual usage, we recommend that you select the highest capacity.

10. Can I still buy shared-performance instances?

Yes.

However, shared-performance instances will be phased out in the future. Please pay attention to the official announcement.

11. Will intranet SLB instances be charged for capacity fee?

  • If the intranet SLB instance is a shared-performance instance, no capacity fee is charged.

  • If the intranet SLB instance is a guaranteed-performance instance, corresponding capacity fee is charged, and no other fees are charged.

Thank you! We've received your feedback.