Shulou(Shulou.com)06/02 Report--

Note that the following categories are divided from the point of view of practical work, and there is no distinction between right and wrong.

1. Benchmark test

It is generally a single-user test, or a test in a zero-data environment.

The aim is to establish a measurable reference standard to provide comparative reference for other test scenarios or tuning processes.

It can also be considered as the most basic performance test.

If the benchmark results do not live up to expectations, then follow-up scenarios are not necessary.

Some errors may be found during testing and resolved to ensure that the script runs smoothly.

two。 Daily stress test

After the benchmark test is passed, the stress test may not be so stressful, and some performance problems will be found and resolved.

3. Peak pressure test

After passing the daily stress test, carry out more stress tests according to the actual situation. Identify performance issues and resolve them.

4. Inflection point test

Find the maximum pressure the system can withstand.

Generally, it is tested by the "inflection point method" to gradually increase the pressure of the system until the performance index is unacceptable or there is an obvious inflection point.

5. Stability test

Verify that the system can run stably for a long time, at least 8 hours.

Verify that some problems are found that cannot be found in a short period of time, such as memory leaks and memory overflows.

Monitor whether the performance indicators are stable and decline.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.