Specifications

RabbitMQ Instance Specifications

DMS for RabbitMQ provides single-node and cluster instances compatible with RabbitMQ 3.7.17. Table 1 and Table 2 list the specifications of RabbitMQ instances.

To ensure stability, the maximum size of a single message is 50 MB. Do not send a message larger than 50 MB.
In the following tables, the reference performance is represented by the number of messages (2 KB each) processed per second. In the tests, persistence and queue mirroring were not enabled. Messages were retrieved immediately after creation and were not accumulated in the queues. The data is for reference only and may differ from that in your production environment.
Performance is related to the queue quantity, message accumulation, number of connections, number of channels, number of consumers, queue mirroring, priority queue, message persistence, and the exchange type. Select instance specifications based on the pressure test result of the service model.
A maximum of 2047 channels can be opened on a connection.

**Table 1** Specifications of single-node RabbitMQ instances
Instance Specifications	Reference Performance (TPS)	Queues (Recommended)	Maximum Connections
2 vCPUs \| 4 GB	10,000	100	2000
4 vCPUs \| 8 GB	20,000	200	3000
8 vCPUs \| 16 GB	35,000	400	5000
16 vCPUs \| 32 GB	45,000	800	8000

**Table 2** Specifications of cluster RabbitMQ instances
Instance Specifications	Brokers	Reference Performance (TPS)	Queues (Recommended)	Maximum Connections
4 vCPUs \| 8 GB	3	45,000	600	3000 x 3
	5	70,000	1000	3000 x 5
	7	80,000	1400	3000 x 7
8 vCPUs \| 16 GB	3	85,000	1200	5000 x 3
	5	110,000	2000	5000 x 5
	7	120,000	2800	5000 x 7
16 vCPUs \| 32 GB	3	130,000	2400	8000 x 3
	5	160,000	4000	8000 x 5
	7	180,000	5600	8000 x 7

Storage Space Selection

In cluster mode, RabbitMQ persists messages to disk. When creating a RabbitMQ instance, select a proper storage space size based on the estimated message size and the number of replicas in a mirrored queue, which can be maximally equal to the number of brokers in the cluster.

For example, if the estimated message size is 100 GB, the disk capacity must be at least: 100 GB x Number of mirrored replicas + 100 GB (reserved).

For single-node instances, select a storage space size based on the estimated message size and the reserved disk space.

You can change the number of brokers in a cluster, but cannot change the specifications of a single-node instance.

Parent topic: Service Overview

Previous topic: Application Scenarios

Next topic: Comparing Kafka and RabbitMQ