How to test performance]

Labels: How to Use OS file data in HTTP Linux

Performance testing uses automated testing tools to simulate a variety of normal, peak, and abnormal load conditions to test the system's performance indicators. Both load testing and stress testing are performance tests, which can be combined. Through the load test, determine the system performance under various workloads, the goal is to test the changes in the system performance indicators when the load increases gradually. Stress testing is to determine the bottleneck of a system or the performance points that cannot be received to obtain the maximum service level tests that the system can provide.

Performance testing includes load testing, strength testing, and Capacity testing.

Load Testing: A load test is a performance test index that runs in an overloaded environment. The load test emphasizes the peak indicators that can be achieved by the system.

Stress Testing: a performance test that runs software systems with low system resources. The Strength Test emphasizes that the system can work stably under high loads, that is, the stability of the system in extreme situations.

 

Capacity Test: determines the maximum number of users that the system can process simultaneously online.

If you want to do a good job of performance testing, you still need to learn a lot. A simple column.

1. proficient in basic concepts, processes, methodologies of performance testing, and understanding of performance engineering;

 

2. proficient in one commercial performance testing tool + one open-source performance testing tool, knowing what the tool can do, what it cannot do, and common problems and solutions in the use of the tool;

 

3. Solid basic computer expertise, including computer composition principles, operating systems, database principles, and computer network principles;

 

4. familiar with at least one common database product, such as SQL Server or Oracle, can perform general database management operations and be familiar with the use of SQL scripts, familiar with common data tuning tools and common counter;

5. familiar with the principle of at least one operating system, Windows or Linux, familiar with the operating system architecture, important basic concepts of the operating system, as well as memory management, storage/file system, Driver/Hardware Management, network protocol implementation and composition, performance monitoring methods and principles, familiar with common counter;

 

6. Be familiar with at least one web server product, such as Apache, and understand General configurations and common counter;

 

7. Be familiar with at least one application server product, such as Tomcat, general configuration, common server performance monitoring methods and principles, and common counter;

8. At least familiar with the TCP/IP protocol and HTTP Protocol. At least familiar with the use and configuration of layer-3, layer-4 switching, or vro. Measure the test taker's knowledge about common counter related to network performance;

9. Understand the deployment architecture and application architecture of general large-scale enterprise applications;

 

10. Understand the architecture and optimization history of well-known ultra-large scale websites with large Web applications, high concurrency, high traffic, and high real-time response requirements;

 

11. Be familiar with basic statistics knowledge, common analysis methods, and experiment design methods, and understand knowledge related to mathematical modeling;

12. Familiar with the business knowledge and user scenarios of the exclusive industry, such as the business knowledge and user scenarios involved in the OSS System of the telecom industry, and the business knowledge and user scenarios involved in the securities trading system;

 

13. A large amount of practical performance testing and optimization experience;

14. Actively participate in discussions and exchanges among various circles and communities.