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

Before we talk about load testing, let's look at a few examples:

Objective:

1. Test the maximum weight that Xiaoming can lift in a short time;

2. The maximum weight that Xiaoming can keep lifting for a long time;

Key point: short time: how short time, 1 second? Two seconds? How long does long mean? A minute? Thirty minutes?

Analysis results: all are the maximum weight that the test Xiaoming can lift in a specified time. The defined time directly affects the test results, that is, the test results are based on a certain premise.

Test Protocol:

1. Try many times to determine

(1) Within the specified time, Xiaoming first tried to lift 50 jin;

(2) If you can lift, try to lift 100 pounds, otherwise try to lift 75 pounds;

(3) If you can lift 100 pounds, try to lift 150 pounds, otherwise try to lift 125 pounds;

(4) Try lifting repeatedly until you find the maximum weight that Xiaoming can lift in the specified time;

Advantages: can quickly find a rough test value, less resources (time, etc.)-because of the exaggeration of the attempt, the number of times;

Disadvantages: It is difficult to find a more accurate test value;

2. Keep trying to determine (it's not appropriate to use people as examples here-after all, people get tired, and it's appropriate if it's applied to computers)

(1) Xiaoming lifted 50 jin first, and then someone started timing synchronously;

(2) During the timing period, Xiaoming maintained a state of lifting 50 jin;

(3) After the end of the first time, someone added 1 jin to Xiaoming and started the second time;(1 jin is only a metaphor, which can be adjusted appropriately according to needs)

(4) Cycle the timer and try to lift it until you find the maximum weight that Xiaoming can lift at the specified time;

Advantages: can find a more accurate test value;

Disadvantages: More resources are consumed-because of continuous testing, the change of test values is slow, and more tests are needed;

Well, I believe you already understand what I mean, that is, to test the maximum load of the software system under specified conditions;

1、

a. From the actual point of view---if the time is short enough, it is a high concurrency stress test. In an extremely short time, the server receives super invincible requests (huge pressure in an instant), tests the performance indicators of the system: response time, number of transactions lost, QPS, etc., and then considers whether the performance indicators meet expectations;

b. Start with requirements-specify system performance metrics (QPS, response time, etc.) and then test the maximum number of requests the system can support in an extremely short period of time;

2、

a. From the actual point of view--if the time is long enough, it is a load test of continuous requests. In an extremely long time, the server continuously receives a certain number of requests, tests the performance indicators of the system (such as response time), and then determines whether the performance indicators meet expectations.

b. Start with requirements---at specified performance metrics (QPS, etc.), and then test the number of requests that the system can support over an extremely long period of time;

3. Generally speaking, the QPS value of short-time stress test is larger than that of long-time load test;

Jmeter test demo late supplement.

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.