Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- 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.
Adding Concurrency Weight Controllers and Throughput Controllers
Concurrency Weight Controller
- Log in to the CodeArts PerfTest console and choose PerfTest Projects in the left navigation pane.
- Click the name of the desired PerfTest project to go to the details page.
- On the Cases tab, select the desired case in the case list on the left.
- On the Case Script tab, choose Add More > Concurrency Weight Controller.
- Set parameters. Up to 10 layers of steps can be nested.
Type: The fixed branch and random branch modes are supported.
- Fixed: Randomly generates a fixed value for all concurrent executions. Subsequent executions use this fixed value to enter a fixed branch. This mode is used to group the concurrencies to simulate parallel tests in multiple scenarios in a case. Using multiple test cases for parallel testing in multiple low-concurrency scenarios requires many executors. You can group test scenarios in a case to save resources.
- Random: Generates a random value for each concurrent execution. Subsequent executions use this random value to enter a random branch. This mode is used to simulate the mixed ratio of the service interface RPS.
The concurrency weight is an integer greater than 0 and less than or equal to 10,000. If there is only one branch, the weight of the branch is 100%. You can click Add Concurrency Weight to add branches.
Figure 1 Concurrency weight controllerFor example:
- Fixed: Assume that there are three low-concurrency test scenarios with 10, 20, and 30 concurrencies, respectively. The total number of concurrencies is 60. Create a test case with 60 concurrencies, set the concurrency weight controller to Fixed, and set the weight ratio to A:B:C = 1:2:3. In this way, the three scenarios are combined into one test case.
- Random: If the peak RPS of a service system is 1,000 (200 on interface A and 800 on interface B), perform the test by selecting Random and setting the weight ratio to A:B = 2:8. In this way, the final ratio of the RPS on interface A to that on interface B is 2:8.
- When the configuration is complete, click Save.
Throughput Controller
- Log in to the CodeArts PerfTest console and choose PerfTest Projects in the left navigation pane.
- Click the name of the desired PerfTest project to go to the details page.
- On the Cases tab, select the desired case in the case list on the left.
- On the Case Script tab, choose Add More > Throughput Controller. Up to 10 layers of steps can be nested.
- Set parameters. Up to 10 layers of steps can be nested.
Set the RPS upper limit. The RPS executed by the controller cannot exceed the preset value. The RPS upper limit is 100 by default. The value can be up to 10 million and accurate to two decimal places.
- When the configuration is complete, click Save.
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