Testing Performance of RocketMQ 4.8.0 Instances (Basic Scenario)

Test Environment

Do as follows to set up the test environment:

1. Buy instances as shown in Table 1. For details about how to buy an instance, see Buying a RocketMQ Instance.

   Table 1 Instance parameters

   Name	Flavor	Brokers	Storage Space	ACL	Public Access	SSL
   rocketmq-01	rocketmq.4u8g.cluster.small	1	Ultra-high I/O 1,500 GB	Enabled	Disabled	Disabled
   rocketmq-02	rocketmq.4u8g.cluster	1	Ultra-high I/O 1,500 GB	Enabled	Disabled	Disabled
   rocketmq-03	rocketmq.8u16g.cluster	1	Ultra-high I/O 1,500 GB	Enabled	Disabled	Disabled
   rocketmq-04	rocketmq.12u24g.cluster	1	Ultra-high I/O 1,500 GB	Enabled	Disabled	Disabled
   rocketmq-05	rocketmq.16u32g.cluster	1	Ultra-high I/O 1,500 GB	Enabled	Disabled	Disabled

2. Create topics as shown in Table 2. For details about how to create topics, see Creating a RocketMQ Topic.

   Table 2 Topic parameters

   Name	Permission	Broker	Queue
   topic-01	Pub/Sub	broker-0	8

3. Create a consumer group as shown in Table 3. For details about how to create a consumer group, see Creating a RocketMQ Consumer Group.

   Table 3 Consumer group parameters

   Name	Broker	Max. Retries	Broadcast
   group-01	broker-0	16	Disabled

4. Create a user as shown in Table 4. For details, see Configuring RocketMQ ACL Users.

   Table 4 User parameters

   Name	Administrator	Default Topic Permissions	Default Consumer Group Permissions	Secret Key
   test	Disabled	Publish/Subscribe	Subscribe	Custom

5. Buy a Linux ECS (with the same region, AZ, VPC, subnet, and security group as the RocketMQ instance). For details about how to purchase an ECS, see Purchasing a Custom ECS.
6. Install Java JDK on the ECS and configure the environment variables JAVA_HOME and PATH.

   export JAVA_HOME=/root/jdk1.8.0_231 
   export PATH=$JAVA_HOME/bin:$PATH

7. Download the benchmark suite.

   wget https://dist.apache.org/repos/dist/release/rocketmq/5.1.4/rocketmq-all-5.1.4-bin-release.zip

8. Decompress the benchmark suite.

   unzip rocketmq-all-5.1.4-bin-release.zip

Test Commands

Production command:

Run the following command in the benchmark folder:

sh producer.sh -n "${Connection address}" -t ${Topic name} -s ${Message size} -w ${Number of producer threads} -a true -ak ${ACL username} -sk ${ACL key}

In the preceding command, -a true indicates that ACL is enabled.

Run the following command with the values obtained in Table 1 to produce a message:

sh producer.sh -n "192.168.111.182:8100;192.168.111.14:8100" -t topic-01 -s 1024 -w 128 -a true -ak test -sk XXXXXXXX

Consumption command:

Run the following command in the benchmark folder:

sh consumer.sh -n "${Connection address}" -t ${Topic name} -g ${Consumer group name} -a true -ak ${ACL username} -sk ${ACL key}

Run the following command with the values obtained in Table 6 to consume messages:

sh consumer.sh -n "192.168.111.182:8100;192.168.111.14:8100" -t topic-01 -g group-01 -a true -ak test -sk XXXXXXXX

Procedure

1. Start the production and consumption commands at the same time.
2. Stop the consumption command 1 minute later and wait for at least 100 GB messages to be produced.
3. Start the consumption command again to test the production and consumption performance in a cold read scenario.

Test Result Reference

The following performance data is of RocketMQ clusters tested based on the benchmark conditions (disk type: ultra-high I/O; message size: 1 KB; cold read scenario). The actual performance is affected by multiple factors including but not limited to the disk type, cold read, cold read concurrency, SSL encryption, ACL, message trace, cross-AZ, production concurrency, and queue traffic distribution. Therefore, you are advised to monitor instances by referring to Configuring RocketMQ Alarms and expand the capacity before the instance performance is insufficient due to service growth.