Updated on 2026-01-07 GMT+08:00

Specifications

DMS for RocketMQ is compatible with open-source RocketMQ 4.8.0 and 5.x. Their specifications are described as follows.

RocketMQ processes messages, relying on the disk throughput. RocketMQ performance baseline is in scenarios where ultra-high I/O and higher disks are used and disk bandwidth is below its upper limit. For details about the impact of disk types on RocketMQ performance, see Does the Disk Type Affect the RocketMQ Instance Performance?

Factors Affecting Performance

The product specification data provided in this section is tested with the baseline (ultra-high I/O disk, 1 KB message for 4.8.0 and 4 KB message for 5.x in the cold read scenario) of a RocketMQ cluster. The actual performance can be affected by multiple factors including but not limited to those listed in Table 1.

Table 1 Factors affecting performance

Factor

Impact

Disk type

The disk performance affects the production performance, and the consumption performance when message stack is large. You are advised to use ultra-high I/O disks or higher.

Cold read or not

When the message stack is small, consumers directly read messages from the memory instead of the disk. On the opposite, they need to read messages from the disk. As a result, the consumption performance deteriorates.

Cold read concurrency

If many consumer groups are to consume large message stacks, disks are randomly read at different offsets, deteriorating consumption performance.

SSL or not

Enabling SSL deteriorates performance.

ACL or not

Enabling ACL deteriorates performance.

Message tracing or not

Enabling message tracing deteriorates performance.

Cross-AZ or not

Cross-AZ production and consumption increase the latency, deteriorating performance.

Production concurrency (number of connections)

Producing by multiple producers concurrently can improve performance. However, it is suggested that the number of connections not exceed the upper limit.

Queue traffic balanced or not

If not, some consumers are more stressed than others. As a result, overall consumption performance deteriorates.

For better RocketMQ performance, the suggestions are as follows:

  • Improve consumption performance through concurrency. Decouple consumer group services. Avoid message stacks to happen on multiple consumer groups at the same time.
  • Use plaintext transmission in intranet access scenarios.
  • Do not specify a queue for sending messages to balance the queue traffic.

DMS for RocketMQ 4.8.0

The specifications of a RocketMQ 4.8.0 instance are defined on seven dimensions:

  • ECS flavor: flavor of the ECS used by the instance
  • Number of brokers: scale of the instance
  • Disk type: defines the storage space. High I/O and ultra-high I/O types are available.
  • Storage space: storage capacity available for each broker
  • TPS per broker: TPS performance of each broker (assuming 1 KB messages as baseline)
  • Max. topics per broker: number of topics allowed for each broker
  • Max. consumer groups per broker: number of consumer groups allowed for each broker

Table 2 lists the flavors of DMS for RocketMQ 4.8.0.

TPS (Transaction per second) indicates the total number of produced and consumed messages per second, that is, the total throughput of message production and consumption per second for a flavor (assuming 1 KB messages).

Table 2 Instance flavors (DMS for RocketMQ 4.8.0)

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

DMS for RocketMQ 5.x Basic Edition

The specifications of a RocketMQ 5.x basic edition instance are defined on six dimensions:

  • ECS flavor: flavor of the ECS used by the instance
  • Disk type: defines the storage space. High I/O and ultra-high I/O types are available.
  • Storage space: storage capacity the instance can use
  • TPS: TPS performance of the instance
  • Max. topics: number of topics allowed for the instance
  • Max. consumer groups: number of consumer groups allowed for the instance

Table 3 and Table 4 list the flavors of DMS for RocketMQ 5.x basic edition. In the following tables, TPS is calculated using 4 KB normal messages. The TPS of sending scheduled, delayed, or transactional messages is that of sending normal messages multiplied by 5. For receiving these messages, do not do the multiplication. For example, the TPS of sending a normal message per second is 1, and TPS of sending a transactional message per second is 5 (1 x 5).

Table 3 Instance flavors (DMS for RocketMQ 5.x basic edition single-node)

Flavor

Storage Space (GB)

TPS

Max. Topics

Max. Consumer Groups

rocketmq.b1.large.1

100–30,000

500

50

500

Table 4 Instance flavors (DMS for RocketMQ 5.x basic edition cluster)

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

DMS for RocketMQ 5.x Professional Edition

The specifications of a RocketMQ 5.x professional edition instance are defined on seven dimensions:

  • ECS flavor: flavor of the ECS used by the instance
  • Disk type: defines the storage space. High I/O, and ultra-high I/O types are available.
  • Storage space: storage capacity the instance can use
  • TPS: TPS performance of the instance
  • Flexible TPS: flexible TPS of the instance
  • Max. topics: number of topics allowed for the instance
  • Max. consumer groups: number of consumer groups allowed for the instance

Table 5 and Table 6 list the flavors of DMS for RocketMQ 5.x professional edition. In the following tables, TPS is calculated using 4 KB normal messages. The TPS of sending scheduled, delayed, or transactional messages is that of sending normal messages multiplied by 5. For receiving these messages, do not do the multiplication. For example, the TPS of sending a normal message per second is 1, and TPS of sending a transactional message per second is 5 (1 x 5).

Table 5 Instance flavors (DMS for RocketMQ 5.x professional edition single-node)

Flavor Name

Storage Space (GB)

TPS

Max. Topics

Consumer Groups

rocketmq.p1.large.1

100–30,000

500

200

500

Table 6 Instance flavors (DMS for RocketMQ 5.x professional edition cluster)

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