Pro Cluster Billing
Last updated: 2025-11-04 14:27:41
This article mainly explains the price of each billing item for TDMQ Pulsar Professional Cluster.
Billable Specification
Cluster specification limits
Max Messaging TPS: Indicates the upper limit on the messaging (production and consumption) TPS of a TDMQ for Apache Pulsar pro cluster.
Note:
The max messaging TPS varies by cluster specification. For more information, see Pro Cluster Specification.
Peak Bandwidth: If it is set to 45 MB/s, both the outbound and inbound bandwidth of the TDMQ for Apache Pulsar pro cluster can reach up to 45 MB/s, including the traffic of three replicas.
Other resource limits: Besides TPS and bandwidth, cluster specifications also vary in terms of certain controlled resources and configuration limits. For details, see Pro Cluster Specification.
Exceeding Specification Limits
Pro Cluster - Fixed Storage
If your actual usage exceeds the upper limit of the purchased cluster, the current platform will not enforce strict throttling measures. We recommend subscribing to alarms for core cluster metrics, monitoring performance changes, and promptly upgrading cluster specifications to ensure stable business operations.
Pro Cluster - Elastic Storage
If your actual usage exceeds the upper limit of the purchased cluster, the platform will perform rate limiting based on the
send-receive ratio configured when creating the cluster, which will affect normal message sending and receiving at that time. We recommend subscribing to alarms for core cluster metrics, promptly upgrading cluster specifications, and ensuring stable business operations.Cluster TPS Compute Specification
1. Message sending and receiving TPS is the total count of messages sent and subscribed to per second.
2. For advanced feature messages, there are two cases:
Scheduled/delayed messages, transaction messages, and Key-Share subscriptions need to multiply the count of calls when sending messages by 5 on the basis of regular messages. For example, when sending 1000 delayed messages per second, the message sending TPS is 1000 × 5 = 5000 times per second.
Tag messages are counted as normal messages in production, while consumption measurement includes filtered messages. For example, if 1000 messages are sent per second, with 2000 message subscriptions and 5000 message filtering, the message sending and receiving TPS is 1000 + 2000 + 5000 = 8000 times per second.
3. Message size uses "4 KB" as the measurement unit, and TPS is calculated with different multipliers based on message size:
Message size | multiplication rate |
N ≤ 4KB | 1 |
4KB < N ≤ 16KB | 2 |
16KB < N ≤ 100KB | 8 |
100KB < N ≤ 1MB | 32 |
1MB < N ≤ 5MB | 128 |
For example, with a message receiving volume of 5,000 per second and a message-sending volume of 5,000 per second, averaging 8 KB per message body size, the message sending and receiving TPS is (8/4) × (5,000+5,000) = 20,000 per second.
Pricing
Cluster Specification Pricing
TDMQ for Pulsar professional cluster divides multi-level gear selections based on the total message sending and receiving TPS and bandwidth peak. Different gear selections mean different computing scales it can handle.
Project | Description |
Billable Items | Billing is based on the specifications of the selected cluster you purchased. |
Billing Mode | Billing Cycle: Based on actual purchase duration. |
Billing Formula | Monthly Subscription: Cluster specification fee = Purchase duration (months) × Unit price (USD/month) |
Unit price | For specific unit price amount, see the actual sales page price. |
Fixed Storage Price
TDMQ for Apache Pulsar pro cluster (fixed storage) allocates fixed storage space to a certain cluster instance. It currently provides SSD Cloud Block Storage as cluster storage, with
3 replicas by default. You may purchase storage space as needed when purchased, with linear charge based on storage size and duration.Storage specification fee = selected specification (GB) × 3 × duration (month) × unit storage price (USD/GB/month)
Region | Cloud Disk Type |
South China (Guangzhou) | 0.1550 |
East China (Shanghai) | 0.1550 |
East China (Nanjing) | 0.1550 |
North China (Beijing) | 0.1550 |
Southwest China (Chengdu) | 0.1550 |
Southwest China (Chongqing) | 0.1550 |
East China (Shanghai Financial Zone) | 0.2728 |
South China (Shenzhen Financial Special Zone) | 0.2728 |
North China (Beijing Finance Zone) | 0.2728 |
Hong Kong (China), Macao (China), and Taiwan (China) | 0.1705 |
Southeast Asia Pacific (Singapore) | 0.1938 |
Southeast Asia Pacific (Jakarta) | 0.1938 |
West US (Silicon Valley) | 0.1783 |
Europe (Frankfurt) | 0.1938 |
Northeast Asia (Seoul) | 0.2015 |
Eastern United States (Virginia) | 0.1938 |
Southeast Asia Pacific (Bangkok) | 0.1938 |
Northeast Asia (Tokyo) | 0.2325 |
South America (São Paulo) | 0.1938 |
Elastic Storage Price
TDMQ for Apache Pulsar pro cluster (elastic storage) performs linear pricing for storage. Storage fees = message storage size × storage unit price × duration.
Note:
Pulsar uses triple-copy message storage by default, so the billing usage storage size is approximately 3 times the total size of the messages monitoring metric.
Unit Price (USD/GB/Hour) as shown in the table below:
Region | Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Qingyuan | Shenzhen Finance, Beijing Finance, Shanghai Finance | Hong Kong (China) | São Paulo, Singapore, Thailand, Jakarta, Virginia, Frankfurt | Seoul, Northeastern Europe | Japan | Silicon Valley |
Unit Price (USD/GB/Hour) | 0.00032551 | 0.00058902 | 0.00038751 | 0.00046502 | 0.00048052 | 0.00054252 | 0.00043401 |
Note:
1. Billing uses the hour as the minimum unit, counts the peak storage value within 1 hour as the actual usage, and charges for a full hour if usage is less than an hour.
2. Settle on an hourly basis, push bills once every 24 hrs, and automatically deduct from account balance.
Cross-Regional Message-Level Replication Pricing
Enabling message-level cross-regional replication tasks will incur fees, while metadata-level will not generate charges. The console provides monitoring metrics to assist with observation.
Billing Description
Billing Item | Calculation Formula | Payment Method | Settlement Method |
Message transmission cost | Message transmission volume (10,000 entries) x Unit price | Postpaid | Settled hourly, get cumulative value, push bill daily |
Task resource occupation | Number of topics x Unit price | Postpaid | Settled daily, get the peak value, calculated on a daily basis if less than a day, push bill daily |
Price
Message Transmission Cost
No. | Message count (hundred million items/month) | Unit Price per Region (USD/10,000 entries) | | |
| | Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Qingyuan | Financial District, Autonomous Driving District | Hong Kong (China), São Paulo, Singapore, Thailand, Jakarta, Virginia, Frankfurt, Seoul, Northeastern Europe, Japan, Silicon Valley |
1 | N < 1 | 0.0138 | 0.0221 | 0.0207 |
2 | 1 ≤ N < 10 | 0.0120 | 0.0199 | 0.0187 |
3 | 10 ≤ N | 0.0111 | 0.0177 | 0.0166 |
Task Resource Occupation
Unit Price (USD/Instance/Day) for Each Region | | |
Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Qingyuan | Financial District, Autonomous Driving District | Hong Kong (China), São Paulo, Singapore, Thailand, Jakarta, Virginia, Frankfurt, Seoul, Northeastern Europe, Japan, Silicon Valley |
0.2766 | 0.4426 | 0.4149 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback