tencent cloud

TDMQ for Apache Pulsar

Release Notes and Announcements
Release Notes
Cluster Version Updates
Product Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for Apache Pulsar
Strengths
Scenarios
How It Works
Product Series
Version Support Instructions for Open-Source Apache Pulsar
Comparison with Open-Source Apache Pulsar
High Availability
Quotas and Limits
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Renewal
Viewing Consumption Details
Overdue Payments
Refund
Getting Started
Getting Started Guide
Preparations
Using the SDK to Send and Receive General Messages
Using the SDK to Send and Receive Advanced Feature Messages
User Guide
Usage Process Guide
Configuring the Account Permission
Creating a Cluster
Configuring the Namespace
Configuring the Topic
Connecting to a Cluster
Managing the Cluster
Querying Messages and Traces
Cross-Region Replication
Viewing Monitoring Data and Configuring Alarm Rules
Use Cases
Client Usage
Abnormal Consumer Isolation
Traffic Throttling Mechanisms
Transaction Reconciliation
Message Idempotence
Message Compression
Migration Guide
Single-Write Multiple-Read Cluster Migration Solutions
Hitless Migration from Virtual Cluster to Pro Cluster
SDK Reference
API Overview
SDK Reference
SDK Overview
Recommended SDK Configuration Parameters
TCP Protocol (Apache Pulsar)
Security and Compliance
Permission Management
Deletion Protection
CloudAudit
FAQs
Monitoring
Clients
Agreements
Service Level Agreement
TDMQ Policy
Contact Us
Glossary
DocumentationTDMQ for Apache PulsarBillingBilling Examples

Billing Examples

PDF
Focus Mode
Font Size
Last updated: 2025-12-24 15:17:18
This article uses an actual billing case of a Pulsar cluster to provide a detailed analysis of the cost composition and calculation methods, helping you understand the specific components of Pulsar instance costs.

Billing Scenarios

Suppose a user purchased a yearly/monthly subscription professional cluster for one month in the Guangzhou region on 2024/04/15 at 13:20:00. After using it for a period, since it failed to meet the business requirements, on 2024/04/20 at 10:00:00, they performed a specification upgrade. The specifications before and after the upgrade are as follows:
Specification
Before Upgrade
After Upgrade
Cluster Specifications
PULSAR.P1.MINI2
PULSAR.P1.MINI4
Disk (Cloud SSD)
200GB
200GB

Billing Composition

Note:
The following prices are for reference only and may not match those on our official website. Actual unit prices are subject to change based on region, promotions, or other policies.
During April - May, the actual costs incurred by this instance are as follows:
Duration
Actual Billing Duration
Billing Mode
Billing Components
Total Cost
2024/04/15 13:20:00~
2024/04/20 10:00:00
2024/04/15 13:00:00~
2024/04/20 10:00:00
117 hours in total
Yearly/monthly subscription
Cluster Specification (PULSAR.P1.MINI2)
Billing unit price = 480.5159 USD/month
Total price = (117/720) x 480.5159 = USD 78.0838
Disk (200 GB)
Billing unit price = 0.1550 USD/GB/month
Total price = (117/720) x 200 x 0.1550 x 3 = USD 15.1125
78.0838 + 15.1125 = USD 93.1963
2024/04/20 10:00:00~
2024/05/15 13:20:00
2024/04/20 10:00:00~
2024/05/15 13:20:00
603 hours in total
Yearly/monthly subscription

Cluster specification (PULSAR.P1.MINI4)
Billing unit price = 1,221.4403 USD/month
Total price = (603/720) x 1,221.4403 = USD 1,022.9563
Disk (200 GB)
Billing unit price = 0.1550 USD/GB/month
Total price = (603/720) x 200 x 0.1550 x 3 = USD 77.8875
1022.9563 + 77.8875 = USD 1100.8438
Total Cost = 93.1963 + 1100.8438 = USD 1194.0401


Previous Topic: Virtual ClustersNext Topic: Renewal

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback