The computing specification is a required billable item of an ApsaraMQ for RocketMQ instance. The computing specification of an instance specifies the peak messaging transactions per second (TPS) on the instance. If the actual TPS usage of your instance exceeds the computing specification limit, the instance is throttled. If a small volume of bursty traffic exists in your business, you can enable the elastic TPS feature for your instance. This way, the messaging TPS of your instance can be increased within a specific range. You are charged for elastic TPS based on the pay-as-you-go billing method.
Background information
The elastic TPS feature is provided by ApsaraMQ for RocketMQ for scenarios in which a small volume of bursty traffic occasionally exists. If you enable the elastic TPS feature, you do not need to reserve a specification that has a high TPS quota for the bursty traffic. You are charged for elastic TPS based on the pay-as-you-go billing method. Compared with TPS in computing specifications, the prices of elastic TPS are higher. If your TPS usage often exceeds the computing specification limit, we recommend that you upgrade the edition of your instance.
The following items describe what happens if the actual messaging TPS usage of an ApsaraMQ for RocketMQ instance exceeds the computing specification limit:
If you enable the elastic TPS feature for the instance and the excess TPS that you use does not exceed the upper limit that is specified by the elastic TPS feature, the instance runs as expected. You are charged for the excess TPS based on the pay-as-you-go billing method. If the excess TPS that you use exceeds the upper limit that is specified by the elastic TPS feature, the instance is throttled.
If the elastic TPS feature is not supported by or enabled for the instance, the instance is throttled.
The elastic TPS feature is supported only by instances that use specific computing specifications. Upper limits are also imposed on the feature. For more information, see Instance specifications.
Billing rules
Item | Description |
Billable item | You are charged for TPS that exceeds the computing specification limit. The billing cycle of elastic TPS is 1 hour. Elastic TPS fees are calculated based on the maximum value of elastic TPS during the 1-hour billing cycle. |
Billing method | You are charged for elastic TPS based on the pay-as-you-go billing method. This billing method allows you to use resources before you pay for the resources. Fees are automatically deducted from the balance of your Alibaba Cloud account. |
Billing cycle | Bills are generated on an hourly basis. A usage period that is shorter than 1 hour is rounded up to 1 hour. |
Formula | Elastic TPS fees = Maximum value of elastic TPS in an hour × Unit price of elastic TPS |
Unit prices of elastic TPS
Primary instance edition | Region | Unit price (USD per TPS-hour) |
Professional Edition | China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London) | 0.00093 |
China (Hong Kong), Singapore, Japan (Tokyo), and UAE (Dubai) | 0.00125 | |
Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), and India (Mumbai) | 0.00135 | |
Enterprise Platinum Edition | China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London) | 0.00186 |
China (Hong Kong), Singapore, Japan (Tokyo), and UAE (Dubai) | 0.00251 | |
Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), and India (Mumbai) | 0.00269 | |
Standard Edition | Standard Edition instances do not support the elastic TPS feature. | N/A |
Billing example
You purchased an ApsaraMQ for RocketMQ Professional Edition instance whose peak TPS in the computing specification is 4,000 and maximum elastic TPS is 2,000 in the China (Shanghai) region. The following table describes the TPS usage of the instance in a specific hour.
Time | 1st minute | 2nd minute | 3rd minute | ... | 59th minute | 60th minute |
Actual TPS usage | 4,100 | 4,200 | 4,500 | < 4,000 | 3,700 | 3,700 |
Elastic TPS | 100 | 200 | 500 | 0 | 0 | 0 |
During the 1-hour billing cycle, the maximum value of elastic TPS is 500. The elastic TPS fee that is incurred by the instance in the hour is USD 0.465. The fee is calculated by using the following formula: 500 × 0.00093 = 0.465.
References
For information about the billing of computing specifications, see Computing fees.
For information about limits on messaging TPS and elastic TPS, see Instance specifications.
For information about the billing methods and billable items of ApsaraMQ for RocketMQ, see Overview.