If you purchase a subscription or pay-as-you-go ApsaraMQ for RocketMQ instance, the computing specification is a required billable item. ApsaraMQ for RocketMQ provides different computing specifications based on peak messaging transactions per seconds (TPS). You are charged computing fees based on the specification size and subscription duration.
Computing specifications
Limits
Messaging TPS
The size of the computing specification of an ApsaraMQ for RocketMQ instance is the peak messaging TPS of the instance.
Computing specifications of different sizes provide different numbers of peak messaging TPS. For more information, see Instance specifications.
Other resource quotas
In addition to the differences in peak messaging TPS, each instance specification may also have different management resources and configuration limits. For more information, see Instance specifications.
What happens if the specification limit is exceeded?
The following items describe what happens if the actual messaging TPS exceeds the specification limit:
If you enable the elastic TPS feature for an 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 a pay-as-you-go basis. If the excess TPS that you use exceeds the upper limit that is specified by the elastic TPS feature, the instance is throttled.
For information about the billing rules of the elastic TPS feature, see Elastic TPS fee.
If the elastic TPS feature is not supported by or enabled for an ApsaraMQ for RocketMQ instance, the instance is throttled.
For information about instance throttling, see Throttling.
Rules for calculating TPS
Messaging TPS is the maximum total number of times that an instance can send and receive messages per second.
By default, the ratio between the message sending TPS and the message receiving TPS on an instance is 1:1. If you require more reads than writes in specific scenarios, you can change the ratio in the ApsaraMQ for RocketMQ console.
The TPS of an instance is calculated based on a message size of 4 KB. A message size that is less than 4 KB is rounded up to 4 KB. For example, 5,000 messages are received and 5,000 messages are sent per second on an instance. If the average message body size of each message is 16 KB, the TPS of the instance is 40,000. The TPS is calculated by using the following formula: (16/4) × (5,000 + 5,000) = 40,000.
For advance-featured messages:
When you calculate the message sending TPS of an instance that is used to send and receive ordered messages, scheduled messages, delayed messages, or transactional messages, a multiplier of five is used.
For example, if 10 transactional messages are sent per second on an instance, the TPS of the instance is 50. The TPS is calculated by using the following formula: 10 × 5 = 50.
When you calculate the message receiving TPS of an instance that is used to send and receive ordered messages, scheduled messages, delayed messages, or transactional messages, a multiplier of five is also used.
Billing rules
You are charged computing fees for an ApsaraMQ for RocketMQ instance based on the specification size. The subscription and pay-as-you-go billing methods are supported. The following table describes the billing details.
Item | Pay-as-you-go | Subscription |
Billable item | You are charged based on the computing specification that you select when you purchase an instance. | You are charged based on the computing specification that you select when you purchase an instance. |
Billing formula | Computing fees = Instance service duration (hours) × Unit price of the specification (USD per hour) Important If you create a pay-as-you-go instance, fees are generated based on the computing specification that you select immediately after you purchase the instance, regardless of whether you connect your applications to the instance. | Computing fees = Subscription duration (months) × Unit price of the specification (USD per month) |
Billing logic | You can create and use an instance without paying for it after you select the computing specification. Fees are generated and paid based on the selected computing specification and service duration after the instance is created, regardless of whether you use the instance to send and receive messages. After a billing cycle ends, a bill is generated and the corresponding fees are deducted from your Alibaba Cloud account. | You can create and use an instance only after you pay for it. You are charged for the instance based on the computing specification and subscription duration that you select. |
Billing cycle | Hourly A service duration that is less than 1 hour is rounded up to 1 hour in a billing cycle. For example, you purchase an instance at 10:30 on a specific day. During the billing cycle from 10:00 to 11:00 on that day, the computing fees of the instance are calculated by using the following formula: Computing fees = 1 hour × Unit price of the specification. | You are charged on a monthly basis. |
Unit price | The unit prices on the buy page shall prevail. | |
FAQ
Why are fees generated even if I did not use a pay-as-you-go instance?
The computing fees of a pay-as-you-go ApsaraMQ for RocketMQ 5.0 instance are generated based on the following rule:
Fees are generated based on the selected computing specification and service duration after an instance is created, regardless of whether you use the instance to send and receive messages.