对于普通实例，Common Microservices Engine (MSE) instances support specifications from 1 vCPU and 2 GiB of memory to 16 vCPUs and 32 GiB of memory. The following tables list the supported connection count, transactions per second (TPS), and provider count for each specification to help you select the right instance size.对于Serverless实例，您无需进行详细的容量评估，系统会根据业务量自动进行弹性伸缩和计费。
Usage notes
-
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 use separate MSE Nacos instances for service discovery and configuration management. If you use a single instance for both, divide the values in Engine types by 2 to estimate instance capabilities.
-
Select instance specifications based on the recommended values. For example, if a Nacos instance requires 1,600 connections, select 4 vCPUs and 8 GiB of memory with 3 nodes, or 2 vCPUs and 4 GiB of memory with 5 nodes.
-
-
If you use Nacos client 1.x, we recommend that you upgrade the engine version to 2.x, or divide the values in Engine types by 2 before estimation. For more information about how to upgrade the engine version, see Upgrade the Nacos engine version.
-
The following tables list estimated values for 3-node instances. You do not need to multiply the values by 3 for capacity planning. For instances with a different node count, scale the values proportionally.
Engine types
-
Number of connections: the number of connections between a Nacos or ZooKeeper client and server. Typically, one connection is established per pod. If both a registry and a configuration center are used, two connections are required.
-
Number of providers: the number of application instances that are registered with an MSE instance.
Nacos
|
Edition |
Specifications |
Number of nodes |
Number of connections |
QPS |
TPS |
|||
|
Security threshold |
Warning threshold |
Security threshold |
Warning threshold |
Security threshold |
Warning threshold |
|||
|
Professional Edition |
1 vCPU and 2 GiB of memory |
3 |
600 |
900 |
600 |
900 |
300 |
450 |
|
2 vCPUs and 4 GiB of memory |
3 |
1,200 |
1,800 |
1,200 |
1,800 |
600 |
900 |
|
|
4 vCPUs and 8 GiB of memory |
3 |
2,400 |
3,600 |
2,400 |
3,600 |
1,200 |
1,800 |
|
|
8 vCPUs and 16 GiB of memory |
3 |
4,800 |
7,200 |
4,800 |
7,200 |
2,400 |
3,600 |
|
|
16 vCPUs and 32 GiB of memory |
3 |
9,600 |
14,400 |
9,600 |
14,400 |
4,800 |
7,200 |
|
|
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 |
|
The Developer Edition is intended for testing or trial use only and cannot be used in production environments.
ZooKeeper
|
Edition |
Specifications |
Number of nodes |
Number of connections |
QPS |
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 intended for testing or trial use only. 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 |