All Products
Search
Document Center

Microservices Engine:Estimate the capabilities of common instances

Last Updated:Jun 03, 2025

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.

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 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 Engine types 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 3 nodes for the instance. You can also select the specifications of 2 vCPUs and 4 GiB of memory and 5 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 Engine types by 2 before the estimation. For more information about how to upgrade the engine version, see Upgrade a Nacos version.

  • The following tables list the estimated values of an instance that has 3 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 tables.

Engine types

Note
  • 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.

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 used for test or trial use scenarios. This edition 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 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