Elastic TPS allows an ApsaraMQ for RocketMQ instance to handle temporary traffic bursts beyond its base messaging computing specification without being throttled. Enable elastic TPS to pay only for the excess TPS on a pay-as-you-go basis, instead of reserving extra capacity.
How it works
Every ApsaraMQ for RocketMQ instance has a base TPS limit defined by its messaging computing specification. When actual send or receive TPS exceeds this limit:
Elastic TPS enabled: The instance operates normally as long as TPS stays within the elastic limit. Excess TPS above the base limit is billed hourly at pay-as-you-go rates. If TPS exceeds the elastic limit, the instance is throttled.
Elastic TPS not enabled or not supported: The instance is throttled immediately.
Tip: Elastic TPS is designed for occasional, short-lived bursts. Because elastic TPS is billed at a higher unit price than the base specification, upgrade the instance type if traffic regularly exceeds the base limit.
Supported editions
| Edition | Elastic TPS support |
|---|---|
| Professional Edition | Supported |
| Platinum Edition | Supported |
| Standard Edition | Not supported |
For the base and elastic TPS limits of each instance type, see Instance types.
Billing
Item | Description |
Billable item | Excess TPS above the base messaging computing specification limit. Measured as the peak TPS increment within each 1-hour billing period. |
Billing method | Pay-as-you-go. Fees are automatically deducted from your Alibaba Cloud account balance. |
Billing cycle | Hourly. Usage under 1 hour is rounded up to 1 hour. |
Formula | Hourly elastic TPS fee = Peak excess TPS in the hour x Unit price per TPS-hour |
Unit prices
Professional Edition
| Region | Unit price (USD/TPS-hour) |
|---|---|
| China (Shanghai), US (Virginia), US (Silicon Valley), Germany (Frankfurt), UK (London) | 0.00093 |
| China (Hong Kong), Singapore, Japan (Tokyo), Mexico, US (Atlanta) | 0.00125 |
| UAE (Dubai) | 0.00186 |
| Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) | 0.00135 |
Platinum Edition
| Region | Unit price (USD/TPS-hour) |
|---|---|
| China (Shanghai), US (Virginia), US (Silicon Valley), Germany (Frankfurt), UK (London) | 0.00186 |
| China (Hong Kong), Singapore, Japan (Tokyo), Mexico, US (Atlanta) | 0.00251 |
| UAE (Dubai) | 0.00371 |
| Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) | 0.00269 |
Billing example
A Professional Edition instance in China (Shanghai) has a base send/receive TPS limit of 4,000 and an elastic TPS limit of 2,000 (allowing up to 6,000 TPS total).
TPS usage during a 1-hour billing period:
Time | 1st minute | 2nd minute | 3rd minute | 4th--59th minute | 60th minute |
Actual TPS | 4,100 | 4,200 | 4,500 | Below 4,000 | 3,700 |
Excess TPS above base | 100 | 200 | 500 | 0 | 0 |
The peak excess TPS during this hour is 500.
Elastic TPS fee = 500 x 0.00093 USD/TPS-hour = 0.465 USD
References
Messaging computing specification fees -- Billing for the base computing specification.
Instance types -- Base and elastic TPS limits for each instance type.
Billing overview -- All billing components and methods for ApsaraMQ for RocketMQ.