CodeArts PerfTest Best Practices

This document summarizes common CodeArts PerfTest operation practices and provides solutions and operation guide to help you easily use CodeArts PerfTest.

**Table 1** CodeArts PerfTest best practices
Practice	Description
Performance Tests of All-in-One Systems for Government Services	Systems related to national economy and people's livelihood, such as all-in-one systems, respond slowly due to sudden increase of access traffic. To prevent system breakdown during peak hours, CodeArts PerfTest simulates actual scenarios and quickly constructs pressure models to detect service performance bottlenecks in different pressure models.
Native Performance Pressure Test of JMeter Test Projects	CodeArts PerfTest supports the native JMeter engine. You can import JMeter scripts into JMeter projects in CodeArts PerfTest to quickly initiate high-concurrency performance tests with JMeter, and view complete performance test reports.
Using Global Variables	Global variables are used to build data sets and enrich test data. If a global variable is used in a request, variable values in the packet will be replaced with specified values during a pressure test.
Using Private Resource Groups to Perform Pressure Tests Through the Private Network in the Same VPC	You can perform a pressure test on backend services via the private network in the same VPC. This method eliminates network interference and lowers test costs. You can systematically verify core components' performance in a highly controllable environment. This is especially suitable for optimizing complex architectures internally and verifying high-risk changes beforehand.