How Many Topics Are Supported?
As shown in Table 1, Table 2, Table 3, Table 4, and Table 5, the number of topics supported varies depending on the instance flavor.
| Flavor | Brokers | Storage Space (GB per Broker) | TPS per Broker | Max. Topics per Broker | Max. Consumer Groups per Broker |
|---|---|---|---|---|---|
| rocketmq.4u8g.cluster.small | 1–10 | 300–30,000 | 15,000 | 2,000 | 2,000 |
| rocketmq.4u8g.cluster | 1–10 | 300–60,000 | 20,000 | 4,000 | 4,000 |
| rocketmq.8u16g.cluster | 1–10 | 300–90,000 | 25,000 | 8,000 | 8,000 |
| rocketmq.12u24g.cluster | 1–10 | 300–90,000 | 28,000 | 12,000 | 12,000 |
| rocketmq.16u32g.cluster | 1–10 | 300–90,000 | 30,000 | 16,000 | 16,000 |
| Flavor | Storage Space (GB) | TPS | Max. Topics | Max. Consumer Groups |
|---|---|---|---|---|
| rocketmq.b1.large.1 | 100–30,000 | 500 | 50 | 500 |
| Flavor | Storage Space (GB) | TPS | Max. Topics | Max. Consumer Groups | Max. Connections |
|---|---|---|---|---|---|
| rocketmq.b2.large.4 | 200–60,000 | 2,000 | 100 | 1000 | 4,000 |
| rocketmq.b2.large.8 | 200–60,000 | 4,000 | 100 | 1000 | 4,000 |
| rocketmq.b2.large.12 | 200–60,000 | 6,000 | 100 | 1000 | 6,000 |
| Flavor Name | Storage Space (GB) | TPS | Max. Topics | Consumer Groups |
|---|---|---|---|---|
| rocketmq.p1.large.1 | 100–30,000 | 500 | 200 | 500 |
| Flavor Name | Storage Space (GB) | TPS | Flexible TPS | Topics | Consumer Groups |
|---|---|---|---|---|---|
| rocketmq.p2.large.8 | 200–60,000 | 4,000 | 2,000 | 400 | 1,500 |
| rocketmq.p2.large.12 | 200–60,000 | 6,000 | 3,000 | 400 | 1,500 |
| rocketmq.p2.large.20 | 200–60,000 | 10,000 | 5,000 | 800 | 1,500 |
| rocketmq.p2.large.40 | 400–120,000 | 20,000 | 10,000 | 800 | 1,500 |
| rocketmq.p2.large.100 | 400–120,000 | 50,000 | 25,000 | 1000 | 2,000 |
| rocketmq.p2.large.150 | 400–120,000 | 75,000 | 37,500 | 1000 | 2,000 |
| rocketmq.p2.large.200 | 800–240,000 | 100,000 | 50,000 | 1,500 | 4,000 |
| rocketmq.p2.large.300 | 800–240,000 | 150,000 | 50,000 | 1,500 | 4,000 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.