- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- CodeArts PerfTest Use Process
- Permissions Management
- Test Resource Management
- PerfTest Project Management
-
PerfTest Case Management
- Test Case Description
- Directory Management of Test Cases
- Creating a Test Case
-
Configuring a Test Case (High-Performance Test Projects)
- Filling in Case Details
- Configuring a Case Script
- Adding Request Information (Packet)
- Adding Request Information (Think Time)
- Adding Request Information (Response Extraction)
- Adding Request Information (Checkpoint)
- Adding a Data Instruction, Cycle Controller, Condition Judgment, or Rendezvous Point
- Adding Concurrency Weight Controllers and Throughput Controllers
- Pressure Configuration
- Advanced Configuration
- SLA Configuration
- Configuring a Test Case (Scalable Test Projects)
- Setting Global Variables (High-Performance Test Projects)
- Setting Global Variables (Scalable Test Projects)
- Binding a Domain Name
- Plug-in Management
- Resetting Configurations
- Managing Test Cases
- Debugging a Case
- Batch Operations
- PerfTest Task Management
- PerfTest Report Management
- Transaction Management
- JMeter Test Project Management
- Crontask
- Configuring SLAs
- Auditing
- Reference
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Resource Group Management
-
Pressure Test Project Management
- What Are the Differences Between Think Time and Duration in CodeArts PerfTest?
- What Is the Number of Concurrent Users?
- How Do I Fill in Packets?
- Why Does Transaction Debugging Frequently Fail?
- Which Headers Are Mandatory in an HTTP-based Packet Request?
- Why Is the CPU Usage of the Execution Node Used for the Pressure Test Constantly High?
- What Are the Differences Between Global Variables and Variables Extracted from Responses?
- What Is the Impact of the Bandwidth Applied for CodeArts PerfTest on Tests?
- What Are the Differences Between a JMeter Test Project and a PerfTest Project?
- How Do I Check If the Global Variable Values Are Read Sequentially in a Test Task?
- Pressure Test Report Management
-
General FAQs
- What Are the Permissions Required for Using CodeArts PerfTest?
- How Do I Use the New IAM Edition to Isolate Permissions by Enterprise Project?
- Does CodeArts PerfTest Support Windows Server 2016 Standard (64-bit)?
- What Can I Do If Chinese or Special Characters Are Not Properly Displayed When the API Response Body Containing Them Is Exported Using the Traffic Recording Plug-in?
-
Using JMeter Projects
- What Are the Differences Between the JMeter Engine of CodeArts PerfTest and the Open-source JMeter?
- What Scripts Does the JMeter Engine of CodeArts PerfTest Support?
- Which Operations in Scripts Are Not Supported by the JMeter Engine of CodeArts PerfTest?
- What Are the Possible Causes of a JMX File Import Error in a JMeter Test Project?
- What Are the Suggestions for Using CodeArts PerfTest Scripts?
- How Do I Use the Global Variable Function?
- What Should I Pay Attention to When Uploading a Third-Party JAR Package?
- What Should I Pay Attention to When Uploading a CSV File?
- What Should I Pay Attention to When Uploading a Custom Installation Package?
- Why Does CodeArts PerfTest Return Garbled Characters When Content-Type in the Request Header Is Set to UTF-8 in JMeter?
- What Are the Meanings of Log Errors in a JMeter Report?
- Why Does JMeter Case Debugging Fail in Less Than 5 Seconds and No Data Is Displayed on the Page?
- Videos
- General Reference
Copied.
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
- If an application is deployed on a node in a cluster, the node cannot be selected to create a private resource group. Do not run any applications or perform other functions on nodes used for test resource groups. Otherwise, applications may run abnormally.
- If you want to perform pressure tests on external services, bind an EIP to each execution node. If you want to debug external services, bind EIPs to both the debugging node and execution node. The test bandwidth is limited by the EIPs' bandwidth.
- 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. These specifications are for reference only. Resource specification requirements for a pressure test 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.
- In a PerfTest test project, one execution node with 8 vCPUs and 16 GB memory supports 10,000 concurrent users. In a JMeter test project, one execution node with 8 vCPUs and 16 GB memory supports 2,000 concurrent users.
Table 1 Recommended node specifications for PerfTest projects Concurrent Users
Specifications
Quantity
0–5,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 4 vCPUs | 8 GB
1
5,001–10,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
1
10,001–20,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
2
20,001–30,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
3
30,001–40,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
4
40,001–50,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
5
More than 50,001
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
n
Table 2 Recommended node specifications for JMeter projects Concurrent Users
Specifications
Quantity
0–1,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 4 vCPUs | 8 GB
1
1,001–2,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
1
2,001–4,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
2
4,001–6,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
3
6,001–8,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
4
8,001–10,000
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
5
More than 10,001
Debugging node: 4 vCPUs | 8 GB
1
Execution node: 8 vCPUs | 16 GB
n
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot