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 PulsarProduct IntroductionProduct SeriesPro Cluster SpecificationsPro Cluster - Elastic Storage

Pro Cluster - Elastic Storage

PDF
Focus Mode
Font Size
Last updated: 2025-12-24 14:51:17
This document describes the specifications of TDMQ for Apache Pulsar pro clusters (elastic storage), including TPS, bandwidth, and the maximum number of topics, for reference during product selection.
Note:
1. The storage system of pro clusters uses three replicas to ensure high data availability.
2. Pro clusters support online specification upgrades. For specific operations, see Upgrading Cluster Specifications. The upgrade process is theoretically imperceptible to businesses. However, clients may experience disconnections and reconnections when the server rebalances topic traffic.
3. TDMQ for Apache Pulsar pro clusters (elastic storage) have a maximum of 100 namespaces regardless of the broker version.

Cluster Specifications

No.
Cluster Specification Code
Maximum TPS for Message Sending and Receiving
Peak Bandwidth (MB/s)
Maximum Number of Topics Per Cluster
Topic x Number of Partitions
Maximum Storage Usage (GB, Including Replicas)
Number of Delayed Messages (Ten Thousand)
1
PULSAR.P2.MINI1
1000
20
200
500
240
200
2
PULSAR.P2.MINI2
2000
45
1000
3000
480
400
3
PULSAR.P2.SMALL4
4000
90
1000
3000
960
800
4
PULSAR.P2.SMALL6
6000
120
1000
3000
1920
1200
5
PULSAR.P2.SMALL10
10000
180
2000
10000
3840
2000
6
PULSAR.P2.MEDIUM15
15000
300
2000
10000
3840
2000
7
PULSAR.P2.MEDIUM20
20000
480
2000
10000
3840
2000
8
PULSAR.P2.MEDIUM40
40000
720
2000
10000
3840
2000
9
PULSAR.P2.MEDIUM60
60000
1080
2000
10000
3840
2000
10
PULSAR.P2.MEDIUM100
100000
1920
3000
20000
11520
4000
11
PULSAR.P2.LARGE150
150000
2400
3000
20000
11520
4000
12
PULSAR.P2.LARGE200
200000
3600
3000
20000
11520
4000
13
PULSAR.P2.LARGE400
400000
4200
3000
20000
11520
4000
14
PULSAR.P2.LARGE600
600000
4800
3000
20000
11520
4000
15
PULSAR.P2.LARGE1000
1000000
6000
3000
20000
11520
4000

Must-Knows

Maximum TPS for Message Sending and Receiving is calculated based on the sum of sent and received general messages with a message size of 4 KB. For advanced feature messages or large messages, the value should be multiplied by the corresponding multiplier. Peak Bandwidth indicates the maximum inbound and outbound bandwidth values. For detailed calculation methods, see Billing Overview of Pro Clusters.
Topic x Number of Partitions indicates the total number of partitions of all topics in a cluster. For example, if a cluster contains 2 topics with 3 partitions each and 1 topic with 2 partitions, Topic x Number of Partitions is 8 (3 x 2 + 2 = 8).

Previous Topic: Message Replicas and Storage MechanismsNext Topic: Pro Cluster - Fixed Storage

Help and Support

Was this page helpful?

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

Feedback