RabbitMQ instances are compatible with RabbitMQ 3.8.35. Table 1 lists the specifications of single-node and cluster RabbitMQ instances.
Flavor | Brokers | Storage Space (GB) | Reference TPS | Maximum Consumers per Broker | Recommended Queues per Broker | Maximum Connections per Broker |
|---|---|---|---|---|---|---|
rabbitmq.2u4g.cluster | 3 | 300–90,000 | 3,000 | 4,000 | 100 | 1,000 |
5 | 500–150,000 | 5,000 | 4,000 | 100 | 1,000 | |
7 | 700–210,000 | 7,000 | 4,000 | 100 | 1,000 | |
rabbitmq.4u8g.cluster | 3 | 300–90,000 | 6,000 | 8,000 | 200 | 2,000 |
5 | 500–150,000 | 10,000 | 8,000 | 200 | 2,000 | |
7 | 700–210,000 | 14,000 | 8,000 | 200 | 2,000 | |
rabbitmq.8u16g.cluster | 3 | 300–90,000 | 12,000 | 16,000 | 400 | 4,000 |
5 | 500–150,000 | 20,000 | 16,000 | 400 | 4,000 | |
7 | 700–210,000 | 28,000 | 16,000 | 400 | 4,000 | |
rabbitmq.12u24g.cluster | 3 | 300–90,000 | 24,000 | 24,000 | 600 | 6,000 |
5 | 500–150,000 | 40,000 | 24,000 | 600 | 6,000 | |
7 | 700–210,000 | 56,000 | 24,000 | 600 | 6,000 | |
rabbitmq.16u32g.cluster | 3 | 300–90,000 | 48,000 | 32,000 | 800 | 8,000 |
5 | 500–150,000 | 80,000 | 32,000 | 800 | 8,000 | |
7 | 700–210,000 | 112,000 | 32,000 | 800 | 8,000 | |
rabbitmq.24u48g.cluster | 3 | 300–90,000 | 60,000 | 40,000 | 1,000 | 10,000 |
5 | 500–150,000 | 100,000 | 40,000 | 1,000 | 10,000 | |
7 | 700–210,000 | 140,000 | 40,000 | 1,000 | 10,000 | |
rabbitmq.32u64g.cluster | 3 | 300–90,000 | 72,000 | 40,000 | 1,000 | 10,000 |
5 | 500–150,000 | 120,000 | 40,000 | 1,000 | 10,000 | |
7 | 700–210,000 | 168,000 | 40,000 | 1,000 | 10,000 |
Old and new RabbitMQ instance flavors are compared as follows.
Old Flavor | New Flavor | ||
|---|---|---|---|
Flavor | Reference TPS | Flavor | Reference TPS |
4 vCPUs | 8 GB × 3 | 3,000 | rabbitmq.4u8g.cluster * 3 | 6,000 |
8 vCPUs | 16 GB × 3 | 6,000 | rabbitmq.8u16g.cluster * 3 | 12,000 |
16 vCPUs | 32 GB × 3 | 24,000 | rabbitmq.16u32g.cluster * 3 | 48,000 |
Instances with new flavors have the following features:
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.