Nacos Stress Test Report¶

This article aims to evaluate the performance of Nacos registry and configuration center under different resource specifications, using JVM virtual machine testing. It will assist you in determining appropriate resource quotas for Nacos based on your actual business scenarios.

Performance Metrics¶

TPS: Transactions Per Second, typically refers to the number of transactions processed by a server per second. In the context of this article, it specifically indicates the number of service registration requests that Nacos server can handle per second.

Test Command¶

java -jar -Xms2g -Xmx2g -Dnacos.server=10.6.222.21:30168 -Dthread.count=100 -Dservice.count=500 nacos-client-1.0-SNAPSHOT-jar-with-dependencies.jar

• -Xms2g: Initial memory allocation for the JVM.
• -Xmx2g: Maximum memory allocation for the JVM.
• -Dnacos.server: Access address of the Nacos registry and configuration center.
• -Dthread.count: Number of threads, corresponding to concurrency in the test results.
• -Dservice.count: Number of requests per thread, corresponding to services in the test results.
• nacos-client-1.0-SNAPSHOT-jar-with-dependencies.jar: Jar package used for stress testing. In actual testing, rename it as nacos-benchmark.jar locally.

Screenshots of the Test Process¶

Test Results¶

Investigating the Impact of JVM Resource Configuration on Nacos Performance¶

To investigate the impact of JVM resource configuration on the performance of hosting Nacos registry and configuration center, we allocated the same resources to JVM as Nacos, which is 2 Core 4 GiB.

The test results under this configuration are as follows:

The TPS remains consistent with the previous results even after adjusting the JVM. This indicates that adjusting the JVM has minimal impact on the performance of Nacos.

Comments