This topic provides the number of connections, transactions per second (TPS) values, and number of providers that are supported for the mainstream specifications of Microservices Engine (MSE) instances. The mainstream specifications include 1 vCPU and 2 GiB of memory, 2 vCPUs and 4 GiB of memory, 4 vCPUs and 8 GiB of memory, 8 vCPUs and 16 GiB of memory, and 16 vCPUs and 32 GiB of memory. You can select the desired specifications for your MSE instance based on the data provided in this topic.
For important environments such as production environments:
We recommend that you select a Professional Edition instance that has more than 2 vCPUs.
We recommend that you create separate MSE Nacos instances for service discovery and configuration management. If you require a single instance to implement service discovery and configuration management, divide data in the following table by 2 to estimate the capabilities of instances.
You must select the instance specifications based on the recommended values. For example, if the number of connections required for a Nacos instance is 1,600, select the specifications of 4 vCPUs and 8 GiB of memory and three nodes for the instance. You can also select the specifications of 2 vCPUs and 4 GiB of memory and five nodes for the instance.
If you use Nacos client 1.x, we recommend that you upgrade the engine version to 2.x, or divide the data in the following table by 2 before the estimation. For more information about how to upgrade the engine version, see Upgrade a Nacos version.
The following table lists 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. If you need 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 table.
Nacos
Edition | Specifications | Number of nodes | Number of connections | TPS | Number of providers |
Professional Edition | 1 vCPU and 2 GiB of memory | 3 | 500 | 650 | 2,500 |
2 vCPUs and 4 GiB of memory | 3 | 1,500 | 2,000 | 7,500 | |
4 vCPUs and 8 GiB of memory | 3 | 3,000 | 4,000 | 15,000 | |
8 vCPUs and 16 GiB of memory | 3 | 6,000 | 8,000 | 30,000 | |
16 vCPUs and 32 GiB of memory | 3 | 12,000 | 16,000 | 60,000 | |
Developer Edition Important The Developer Edition is used for test or trial use scenarios. It cannot be used in production environments. | 1 vCPU and 2 GiB of memory | 1 | 50 | 65 | 250 |
2 vCPUs and 4 GiB of memory | 1 | 150 | 200 | 750 | |
Basic Edition (discontinued) | 1 vCPU and 2 GiB of memory | 3 | 250 | 300 | 1,000 |
2 vCPUs and 4 GiB of memory | 3 | 750 | 1,000 | 3,500 | |
4 vCPUs and 8 GiB of memory | 3 | 1,500 | 2,000 | 7,500 | |
8 vCPUs and 16 GiB of memory | 3 | 3,000 | 4,000 | 15,000 | |
16 vCPUs and 32 GiB of memory | 3 | 6,000 | 8,000 | 30,000 |
ZooKeeper
Edition | Specifications | Number of nodes | Number of connections | TPS | Number of providers |
Professional Edition | 1 vCPU and 2 GiB of memory | 3 | 800 | 900 | 4,000 |
2 vCPUs and 4 GiB of memory | 3 | 2,000 | 2,300 | 10,000 | |
4 vCPUs and 8 GiB of memory | 3 | 3,000 | 4,000 | 15,000 | |
8 vCPUs and 16 GiB of memory | 3 | 6,000 | 8,000 | 30,000 | |
16 vCPUs and 32 GiB of memory | 3 | 12,000 | 16,000 | 60,000 | |
Developer Edition Important The Developer Edition is used for test or trial use scenarios. It cannot be used in production environments. | 1 vCPU and 2 GiB of memory | 1 | 50 | 60 | 250 |
2 vCPUs and 4 GiB of memory | 1 | 150 | 210 | 1,050 |
Number of connections: The number of connections that are established between a Nacos or ZooKeeper client and a Nacos or ZooKeeper server. In most scenarios, one connection is established for a pod. However, if a registry and a configuration center are used at the same time, two connections must be established.
Number of providers: The number of application instances that are registered with an MSE instance.