Suggestions on Test Resource Configuration

Test Resource Groups and Their Constraints

Test resource groups are classified into shared resource groups and private resource groups. Shared resource groups are provided by the system by default, and private resource groups need to be created.
Execution nodes of the shared resource group have been bound with an elastic IP address (EIP). When the tested application has network access restrictions, use a private resource group.
A shared resource group supports a maximum of 1,000 concurrent users and 100 Mbit/s bandwidth. If higher concurrency or bandwidth is required, use a private resource group.
JMeter test tasks can use only private resource groups.

Suggestions on Using Nodes

Do not run any applications or perform other functions on nodes used for test resource groups. Otherwise, applications may run abnormally.
Create at least two empty nodes. One is for debugging an execution node. The other is the execution node/executor (a target machine that a pressure test will be performed on and can provide performance data during testing). Create nodes of the required specifications based on the number of concurrent users for a pressure test. For details about the recommended node specifications, see Table 1 and Table 2.

If you want to perform pressure tests on external services, bind an EIP to the execution node. If you want to debug external services, bind EIPs to both the debugging node and execution node.

**Table 1** Recommended node specifications for PerfTest projects
Concurrent Users	Specifications	Quantity
0–5,000	Debugging node: 4 vCPUs \| 8 GB	1
0–5,000	Execution node: 4 vCPUs \| 8 GB	1
5,001–10,000	Debugging node: 4 vCPUs \| 8 GB	1
5,001–10,000	Execution node: 8 vCPUs \| 16 GB	1
10,001–20,000	Debugging node: 4 vCPUs \| 8 GB	1
10,001–20,000	Execution node: 8 vCPUs \| 16 GB	2
20,001–30,000	Debugging node: 4 vCPUs \| 8 GB	1
20,001–30,000	Execution node: 8 vCPUs \| 16 GB	3
30,001–40,000	Debugging node: 4 vCPUs \| 8 GB	1
30,001–40,000	Execution node: 8 vCPUs \| 16 GB	4
40,001–50,000	Debugging node: 4 vCPUs \| 8 GB	1
40,001–50,000	Execution node: 8 vCPUs \| 16 GB	5
More than 50,001	Debugging node: 4 vCPUs \| 8 GB	1
More than 50,001	Execution node: 8 vCPUs \| 16 GB	n NOTE: Each execution node (8 vCPUs \| 16 GB) supports 10,000 concurrent users.

**Table 2** Recommended node specifications for JMeter projects
Concurrent Users	Specifications	Quantity
0–1,000	Debugging node: 4 vCPUs \| 8 GB	1
0–1,000	Execution node: 4 vCPUs \| 8 GB	1
1,001–2,000	Debugging node: 4 vCPUs \| 8 GB	1
1,001–2,000	Execution node: 8 vCPUs \| 16 GB	1
2,001–4,000	Debugging node: 4 vCPUs \| 8 GB	1
2,001–4,000	Execution node: 8 vCPUs \| 16 GB	2
4,001–6,000	Debugging node: 4 vCPUs \| 8 GB	1
4,001–6,000	Execution node: 8 vCPUs \| 16 GB	3
6,001–8,000	Debugging node: 4 vCPUs \| 8 GB	1
6,001–8,000	Execution node: 8 vCPUs \| 16 GB	4
8,001–10,000	Debugging node: 4 vCPUs \| 8 GB	1
8,001–10,000	Execution node: 8 vCPUs \| 16 GB	5
More than 10,001	Debugging node: 4 vCPUs \| 8 GB	1
More than 10,001	Execution node: 8 vCPUs \| 16 GB	n NOTE: Each execution node (8 vCPUs \| 16 GB) supports 2,000 concurrent users.

Specifications of the preceding nodes are for reference only. During a pressure test, resource specifications are affected by think time, protocol type, the size and number of requests and responses, response time, and result verification. Adjust the specifications based on your requirements.
Bind an EIP to an execution node to perform a pressure test on an external service. The test bandwidth depends on the EIP bandwidth you purchased.
If an application is deployed on a node in a cluster, the node cannot be used to create a private resource group.

Parent topic: Resource Group Management