This document mainly describes the specifications of the TDMQ for Apache Pulsar Pro cluster (fixed storage), including TPS, bandwidth, and topic quantity limit. They are used for your selection and usage.
Note:
1. Pro cluster storage uses a triple replica mechanism to ensure data high availability.
2. Pro clusters support online upgrade configuration. For specific operations, see the document Upgrading Cluster. Theoretically, the upgrade process should be seamless for the business. However, during server-side Rebalance Topic operations, clients may experience disconnections followed by reconnections. Pro Cluster Specification
|
1 | PULSAR.P1.MINI2 | 2000 | 45 | 1000 | 200 |
2 | PULSAR.P1.SMALL4 | 4000 | 90 | 1000 | 200 |
3 | PULSAR.P1.SMALL6 | 6000 | 120 | 1000 | 267 |
4 | PULSAR.P1.SMALL10 | 10000 | 180 | 2000 | 400 |
5 | PULSAR.P1.MEDIUM15 | 15000 | 300 | 2000 | 333 |
6 | PULSAR.P1.MEDIUM20 | 20000 | 480 | 2000 | 400 |
7 | PULSAR.P1.MEDIUM40 | 40000 | 720 | 2000 | 533 |
8 | PULSAR.P1.MEDIUM60 | 60000 | 1080 | 2000 | 533 |
9 | PULSAR.P1.MEDIUM100 | 100000 | 1920 | 3000 | 533 |
10 | PULSAR.P1.LARGE150 | 150000 | 2400 | 3000 | 667 |
11 | PULSAR.P1.LARGE200 | 200000 | 3600 | 3000 | 800 |
12 | PULSAR.P1.LARGE400 | 400000 | 4200 | 3000 | 1000 |
13 | PULSAR.P1.LARGE600 | 600000 | 4800 | 3000 | 1200 |
14 | PULSAR.P1.LARGE1000 | 1000000 | 6000 | 3000 | 1667 |
Notes
The max messaging TPS is calculated based on the general message type and message size of 4 KB. The values for advanced messages and large messages need to be multiplied accordingly. The peak bandwidth indicates the maximum inbound and outbound bandwidth. For specific calculation methods, see Pro Cluster Billing.
Was this page helpful?