Help Center/
CodeArts PerfTest/
Best Practices/
Performance Tests of All-in-One Systems for Government Services/
Operation Process
Updated on 2024-07-31 GMT+08:00
Operation Process
Perform the following operations before using CodeArts PerfTest:
- (Optional) Basic Concepts of CodeArts PerfTest: Understand some basic concepts.
- Prerequisites: Prepare an application to be tested.
- Preparing Test Resources: Purchase a proper CodeArts PerfTest package. Create a private resource group. If a shared resource group is used for testing, you do not need to create a resource group.
- Creating, Debugging, and Starting a Task: Create a pressure test task based on your service requirements. Multiple tasks can be executed concurrently.
- Test Report Analysis: View real-time reports and identify performance bottlenecks of an all-in-one system.
Basic Concepts of CodeArts PerfTest
- Number of concurrent users: number of users performing operations on a system at the same time. In CodeArts PerfTest, it is the number of virtual users you define when you configure a test phase.
- RPS (QPS): average number of requests sent per second (RPS = Requests / Taken Time (s)).
- Response Time: duration from the time when a client sends a request to the time when the client receives a response from the server.
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot