TDMQ for Apache Pulsar
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Pricing Overview
- Pro Cluster
- Getting Started
- Using SDK to Send and Receive Normal Messages
- Developer Guide
- How It Works
- Operation Guide
- Cluster Management
- Monitoring and Alarms
- Permission Management
- Pulsar Instance Permission Management
- Cross-Region Replication
- Practical Tutorial
- API Documentation
- Making API Requests
- Cluster APIs
- Namespace APIs
- CMQ Management APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- SDK Documentation
- Apache Pulsar TCP Protocol
- General References
Pro Cluster Billing
Last updated: 2025-04-01 11:16:44
This document describes the billing mode of TDMQ for Apache Pulsar pro cluster.
Billable Items
TDMQ for Apache Pulsar pro cluster is monthly subscribed (prepaid) with the following billable items:
Cluster specifications
Storage specifications
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.
Exceeded Specification Limits
Pro Cluster - Fixed Storage
If your actual usage exceeds the purchased cluster's specification limit, the current platform will not implement throttling measures (expected to be launched in Q3 2024). It is recommended to subscribe to the alarms for the cluster's core metrics, pay attention to metric changes and corresponding performance, promptly upgrade the cluster specification, and ensure stable business operation. We will consider providing elasticity in the future to avoid this issue.
Pro Cluster - Elastic Storage
If your actual usage exceeds the purchased cluster's specification limit, based on the
sending/receiving ratio that you configured when creating the cluster, the platform will implement throttling . This will affect the normal sending and receiving of messages. It is recommended to subscribe to the cluster's core metric alarms and promptly upgrade the cluster specification to ensure stable business operation.Cluster TPS Specification
1. Messaging TPS refers to the maximum sum of messages sent and subscribed per second.
2. For advanced feature messages, there are two scenarios:
For scheduled/delayed messages, transaction messages, and Key-Share subscription, the number of calls when sending messages should be multiplied by a factor of 5 times the rate of normal messages. For example, sending 1,000 delayed messages per second would result in a message send TPS of 1,000 x 5 = 5,000 times/second.
For tag messages, production is calculated as normal messages, and the filtered message count will be increased in consumption measurement. For example, sending 1,000 messages per second, with a message subscription volume of 2,000 and a message filtered volume of 5,000, the message sending/receiving TPS would be 1,000 + 2,000 + 5,000 = 8,000 times/second.
3. Message size is measured in 4 KB, and TPS is calculated based on different multiples depending on message size:
Message size | Multiples |
N ≤ 4 KB | 1 |
4KB < N ≤ 16KB | 2 |
16 KB < N ≤ 100 KB | 8 |
100 KB < N ≤ 1 MB | 32 |
1 MB < N ≤ 5 MB | 128 |
For example, if the message receiving volume is 5,000 messages per second, and the message sending volume is 5,000 messages per second, with an average message body size of 8 KB, then the message sending and receiving TPS is (8/4)x(5,000+5,000)=20,000 times/second.
Billing Description
Cluster specification billing
TDMQ for Apache Pulsar pro cluster provides different computing specifications determined by the messaging TPS and peak bandwidth.
Item | Description |
Billable item | Fees are charged based on the purchased cluster specification. |
Billing method | Billing cycle: It is subject to the actual validity period of the cluster. |
Billing formula | Monthly subscription: Cluster specification fees = validity period (month) x unit price (USD/month). |
Unit price | It is subject to the price on the purchase page. |
Fixed Storage Costs
TDMQ for Apache Pulsar pro cluster provides SSD to store cluster data with three replicas by default. You can purchase the storage space as needed.
Item | Description |
Billable item | Fees are charged based on the storage specification configured during cluster purchase. |
Billing method | Billing cycle: It is subject to the actual validity period of the cluster. |
Billing formula | Monthly subscription: Storage specification fees = selected specification (GB) 3 validity period (month) * unit price (USD/GB/month). |
Unit price | See the table below. |
Storage unit price
Unit: USD/GB/month
Region | Cloud Disk Type |
| SSD |
South China (Guangzhou) | 0.1397 |
East China (Shanghai) | 0.1397 |
East China (Nanjing) | 0.1397 |
North China (Beijing) | 0.1397 |
Southwest China (Chengdu) | 0.1397 |
Southwest China (Chongqing) | 0.1397 |
East China (Shanghai Finance Zone) | 0.2458 |
South China (Shenzhen Finance Zone) | 0.2458 |
North China (Beijing Finance Zone) | 0.2458 |
Hong Kong, Macao and Taiwan, China (Hong Kong) | 0.1536 |
Southeast Asia (Singapore) | 0.1746 |
Southeast Asia (Jakarta) | 0.1746 |
West US (Silicon Valley) | 0.1606 |
Europe (Frankfurt) | 0.1746 |
Northeast Asia (Seoul) | 0.1816 |
East US (Virginia) | 0.1746 |
Southeast Asia Pacific (Bangkok) | 0.1746 |
Northeast Asia (Tokyo) | 0.2095 |
South America (São Paulo) | 0.1746 |
Elastic Storage Costs
TDMQ for Apache Pulsar pro cluster (elastic storage) employs linear pricing for storage. Storage Costs = Message Storage Size x Storage Unit Price x Duration .
Note
Pulsar by default stores messages in three replicas, so the billed storage size is approximately three times the total size of the monitored messages.
The following table shows the storage unit price (Unit: USD/GB/hour):
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 is calculated on an hourly basis, with the peak storage value within an hour considered as the actual usage. Any time less than one hour is billed as one hour.
2. Settlement occurs every hour, and a bill is pushed every 24 hours. The costs will be automatically deducted from the account balance.
Cross-Regional Message-Level Replication Fee
When you enable cross-region replication tasks at the message level, fees will be incurred, while no fees will be generated at the metadata level. The console provides corresponding monitoring metrics to assist in observation.
Billing Item Description
Billing Item | Computation Formula | Payment Method | Settlement Method |
Message Transfer Fee | Message transmission volume (10,000 entries) x Unit price of message transmission | Postpaid | Settle by hour, get cumulative message value, and push bills daily. |
Task resource occupancy | Number of topics in the task x unit price of task resource | Postpaid | Settle by day, get the peak value of each day. If it is less than one day, calculate it as one day and push bills daily. |
Pricing
Message Transfer Fee
No. | Message count (hundred million items/month) | <Unit Price (USD/10,000 entries) in Each Region> | | |
| | Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Qingyuan | Financial district, Autonomous driving zone | Hong Kong (China), São Paulo, Singapore, Thailand, Jakarta, Virginia, Frankfurt, Seoul, Northeastern Europe, Japan, Silicon Valley |
1 | N < 1 | 0.014 | 0.022 | 0.021 |
2 | 1 ≤ N < 10 | 0.012 | 0.020 | 0.018 |
3 | 10 ≤ N | 0.011 | 0.018 | 0.016 |
Task Resource Occupancy
Unit Price in Each Region (USD/Instance/Day) | | |
Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Qingyuan | Financial district, Autonomous driving zone | Hong Kong (China), São Paulo, Singapore, Thailand, Jakarta, Virginia, Frankfurt, Seoul, Northeastern Europe, Japan, Silicon Valley |
0.274 | 0.438 | 0.411 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No