this topic provides the number of connections, queries per second (QPS), and transactions per second (TPS) supported by mainstream specifications. These specifications include 1 Core 2 GiB, 2 Core 4 GiB, 4 Core 8 GiB, 8 Core 16 GiB, and 16 Core 32 GiB. This information helps you select component specifications based on your needs.
Usage notes
For important environments such as production environments:
Select a Professional Edition cluster with more than 2 cores or an Enterprise Edition cluster of any specification.
If you use both service discovery and configuration management, create separate MSE Nacos clusters for each scenario.
Strictly plan cluster specifications based on the recommended values. For example, if the number of Nacos connections reaches 1,920, select a 3-node cluster with 4 cores and 8 GiB of memory.
The following tables list the estimated values of an instance that has three nodes. Therefore, you do not need to multiply the estimated values by 3 for capacity planning if you want to use such instances. To estimate the capabilities of an instance whose node quantity is not 3, you can perform estimation by proportionally increasing the estimated values in the following tables.
Engine types
Nacos
Number of connections: The number of connections established between Nacos clients and the server. In a typical scenario, one pod establishes one connection. However, if you use a registry and a configuration center at the same time, two connections must be established.
Level assessment: For core services, keep capacity metrics below the safe level to ensure high stability during sudden traffic bursts. When QPS or TPS reach the warning level, traffic bursts may cause stability risks. Also, keep capacity metrics below the safe level when you restart or upgrade a cluster.
Assessment criteria: To ensure the stability of MSE Nacos, the following capacity assessment is based on client version 1.x. For optimal performance, upgrade the client to version 2.x.
Edition | Specifications | Number of nodes | Number of connections | Queries per second (QPS) | Transactions per second (TPS) | |||
Safe level | Warning level | Safe level | Warning level | Safe level | Warning level | |||
Professional Edition | 1 vCPU and 2 GiB of memory | 3 | 480 | 720 | 480 | 720 | 240 | 360 |
2 vCPUs and 4 GiB of memory | 3 | 960 | 1,440 | 960 | 1,440 | 480 | 720 | |
4 vCPUs and 8 GiB of memory | 3 | 1,920 | 2,880 | 1,920 | 2,880 | 960 | 1,440 | |
8 vCPUs and 16 GiB of memory | 3 | 3,840 | 5,760 | 3,840 | 5,760 | 1,920 | 2,880 | |
16 vCPUs and 32 GiB of memory | 3 | 7,680 | 11,520 | 7,680 | 11,520 | 3,840 | 5,760 | |
Developer Edition | 1 vCPU and 2 GiB of memory | 1 | 50 | 75 | 50 | 75 | 25 | 40 |
2 vCPUs and 4 GiB of memory | 1 | 150 | 225 | 150 | 225 | 75 | 120 | |
Developer Edition is for development, testing, or product trial purposes. Do not use it in production environments.
ZooKeeper
For newly purchased instances of version 3.8.0.9, rate limiting is automatically enabled. If your usage reaches the warning level, traffic is rate-limited. Monitor your capacity and configure capacity alerts to prevent stability risks caused by rate limiting.
Version | Specifications | Number of nodes | Connections | Storage size limit | Number of watches | |||
Safe level | Warning level | Safe level | Warning level | Safe level | Warning level | |||
Professional Edition | 1 Core 2 GiB | 1 | 330 | 500 | 33 MB | 50 MB | 330,000 | 500,000 |
2 Core 4 GiB | 1 | 660 | 1,000 | 66 MB | 100 MB | 3,000,000 | 3,000,000 | |
4 Core 8 GiB | 1 | 1,320 | 2,000 | 165 MB | 250 MB | 462 W | 7,000,000 | |
8 Core 16 GiB | 1 | 2,640 | 4,000 | 330 MB | 500 MB | 660 W | 10,000,000 | |
16 Core 32 GiB | 1 | 5,280 | 8,000 | 660 MB | 1 GB | 1320 W | 20,000,000 | |
Developer Edition Important Developer Edition is for development, testing, or product trial purposes. Do not use it in production environments. | 1 Core 2 GiB | 1 | 66 | 100 | 16 MB | 25 MB | 160,000 | 25 W |
2 Core 4 GiB | 1 | 132 | 250 | 33 MB | 50 MB | 330,000 | 500,000 | |
Anti-fragility rate limiting
To ensure the stability of MSE Nacos, an anti-fragility mode is enabled by default for Professional Edition instances purchased on or after July 24, 2025. When the capacity of certain resources or the traffic on specific engine-side interfaces reaches a threshold, the engine applies capacity and rate limits to maintain stability.
The following table lists the rate limiting rules for a single-node scenario. To determine the rate limiting rules for a cluster with a different number of nodes, scale the data for a single node of the same specification proportionally.
Specifications | Connections | Same configuration publishes (times/minute) | Configuration publishes (TPS) | Configuration queries (TPS) | Service pushes (TPS) |
1 Core 2 GiB | 320 | 20 | 80 | 80 | 320 |
2 Core 4 GiB | 640 | 20 | 80 | 160 | 640 |
4 Core 8 GiB | 1,280 | 20 | 80 | 320 | 1,280 |
8 Core 16 GiB | 2,560 | 20 | 80 | 640 | 2,560 |
16 Core 32 GiB | 5,120 | 20 | 80 | 1,280 | 5,120 |