This document mainly describes the prices of each billable item for standard clusters in TDMQ for Apache Pulsar.
Billing Specifications
Limits of Cluster Specifications
Maximum TPS for Message Sending and Receiving: refers to the maximum TPS at which a TDMQ for Apache Pulsar standard cluster can process message sending and receiving (production + consumption).
Upper limit of peak bandwidth: Taking 45 MB/s as an example, this means the inbound and outbound bandwidth of the TDMQ for Apache Pulsar standard cluster can each reach 45 MB/s.
Other resource limits: Cluster specifications differ not only in TPS and bandwidth capabilities, but also in certain management resources and configuration limits. For the specific limits of each specification, see Standard Cluster Specifications. After the Limits of Cluster Specifications Are Exceeded
Standard Cluster - Elastic Storage
If your actual usage exceeds the specification limit of the purchased cluster, the platform will throttle traffic based on the sending and receiving ratio configured when you created the cluster, which will affect normal message sending and receiving. You can enable the elastic TPS switch in the console to increase the elastic TPS limit without upgrading the cluster specifications. It is recommended that you subscribe to alarms for core cluster metrics so that you can upgrade the specifications or enable elastic TPS in a timely manner when usage is too high, ensuring business stability. For detailed instructions, see Elastic TPS. TPS Calculation Rules
1. The TPS for message sending and receiving refers to the total number of messages sent and subscribed per second.
2. For messages with advanced features, there are two scenarios:
For scheduled/delayed messages, transactional messages, and Key-Shared subscriptions, the number of API calls for sending and subscribing to messages must be multiplied by a multiplier of 5 compared to general messages. For example, sending 1,000 delayed messages per second results in a message sending TPS of 1,000 × 5 = 5,000 times/second, and subscribing to 1,000 delayed messages per second results in a message subscription TPS of 1,000 × 5 = 5,000 times/second.
For tag messages, production is calculated as normal messages, and during consumption, the metering includes the volume of filtered messages. For example, sending 1,000 messages per second, with a message subscription volume of 2,000 and a message filtering volume of 5,000, results in a message sending and receiving TPS of 1,000 + 2,000 + 5,000 = 8,000 times/second.
3. Message size is measured in 4 KB units, and TPS is calculated with different multipliers based on the message size:
|
N ≤ 4KB | 1 |
4KB < N ≤ 16KB | 2 |
16KB < N ≤ 100KB | 8 |
100KB < N ≤ 1MB | 32 |
1MB < N ≤ 5MB | 128 |
For example, if 5,000 messages are received and 5,000 messages are sent per second, with an average message body size of 8 KB, the TPS for message sending and receiving is (8/4) × (5,000 + 5,000) = 20,000 times/second.
Cluster Pricing Details
Cluster Computing Pricing
TDMQ for Apache Pulsar standard clusters are divided into multiple tiers based on the total TPS for message sending and receiving and peak bandwidth, with each tier corresponding to different computing scale capacities. The current billing rules and corresponding descriptions for the standard edition clusters are as follows:
|
Billable item | Billed based on the cluster specifications you purchased. |
Billing mode | Billing cycle: determined by the actual duration you purchased. |
Billing formula | Yearly/monthly subscription: cluster specification fee = purchase duration (month) × unit price (CNY/month). |
Billing unit price | For specific unit prices, see the actual sales page. |
Cluster Storage Pricing
The storage method of the Pulsar standard edition is elastic storage, which supports linear pricing for storage. The billing logic is: Storage fee = Message storage size x Storage unit price x Duration. The storage unit price (unit: CNY/GB/hour) is shown in the following table:
|
Unit price (CNY/GB/hour) | 0.0021 | 0.0038 | 0.0025 | 0.003 | 0.0031 | 0.0035 | 0.0028 |
Note:
1. Billing is calculated on an hourly basis, with the peak storage usage within each hour counted as the actual consumption. Any duration less than one hour is billed as a full hour.
2. Settlement is performed hourly, bills are pushed every 24 hours, and fees are automatically deducted from your account balance.
3. Due to resource scale limitations, elastic storage is not available in all regions. To see the regions where elastic storage is available, go to the purchase page. Elastic TPS Pricing
Only the elastic storage clusters of the Standard Edition support the "elastic TPS" feature and incur this fee.
The elastic TPS billing method for TDMQ for Apache Pulsar clusters is pay-as-you-go (postpaid). The billing unit is "XX CNY/TPS/hour". Settlement is performed hourly, and fees are charged daily. Any usage less than 1 hour is billed as 1 hour.
Hourly elastic TPS fee = Maximum incremental TPS value within 1 hour x Unit price of elastic TPS.
Note:
Take the Guangzhou region as an example. A standard elastic storage cluster originally had a TPS specification of 6,000. After elastic TPS was enabled, an additional 4,000 elastic TPS was added, bringing the total TPS to 10,000. If the total TPS peaked at 9,000 within one hour, the fee for that hour would be calculated as unit price 0.006 × the excess 3,000 TPS × 1 hour = CNY 18.
|
Standard Edition Elastic storage | 1000 | 1000 | 0.006 | 0.0078 | 0.0096 |
| 2000 | 2000 |
|
|
|
| 4000 | 2500 |
|
|
|
| 6000 | 4000 |
|
|
|
| 10000 | 6000 |
|
|
|
Public Network Pricing
Public network bandwidth fees are calculated based on the bandwidth size you purchase and the usage duration. Currently, only the monthly subscription billing mode is supported.
|
| Beijing, Guangzhou, Shanghai, Shenzhen Finance, Nanjing, Chengdu | Hong Kong (China), Silicon Valley, Virginia, Riyadh, Sao Paulo | Singapore, Johor Bahru, Frankfurt | Bangkok, Tokyo, Seoul | Shanghai Autonomous Driving Zone |
1Mbps | 23 | 30 | 23 | 25 | 34.5 |
2Mbps | 46 | 60 | 46 | 50 | 69 |
3Mbps | 71 | 90 | 69 | 75 | 106.5 |
4Mbps | 96 | 120 | 92 | 100 | 144 |
5Mbps | 125 | 150 | 115 | 125 | 187.5 |
6 Mbps or above (n is the configured bandwidth limit) | 125 + 80 ×(n - 5) | 150 + 100 ×(n - 5) | 115 + 80 ×(n - 5) | 125 + 80 ×(n - 5) | 187.5 + 120 ×(n - 5) |