Jmeter performance test - stress mode

stress mode

There are two stress modes in performance testing.

The first is concurrent user mode (virtual user mode). Concurrent users refer to the number of virtual concurrent users. From a business perspective, it can also be understood as the number of concurrent online users.

From the perspective of the client, to find out the number of online users that each node of the business system can carry at the same time, you can use this mode to set the target concurrency, that is, the number of threads in Jmeter.

The second is RPS mode (throughput mode). RPS (Requests Per Second) refers to the number of requests per second. The RPS mode is the "throughput mode". By setting the number of requests sent per second, from the perspective of the server, the throughput capacity of the system is directly measured.

Requirement 1: There is a project, 500 users log in at the same time, what is the response time?

Scenario analysis: This is a typical concurrent user mode.

When we design the first scenario with Jmeter, we can use the number of threads to simulate concurrent users.

Set 500 threads to simulate 500 users as shown in the figure below; one iteration means that the request of each thread is only initiated once; the rendezvous point 500 means that the 500 threads will initiate the request at the same time, add a listener to view the response time

Requirement 2: What is the maximum throughput of time and attendance check-in? (The maximum number of check-in transactions that can be completed per second)

Scenario Analysis: This is the typical throughput mode.

Why design this mode? When the leader asked to do the performance test, he didn't know the specific number of concurrency and the number of visits to the system. Is there no way for us to test such a picture?

We need to think about throughput. The inflection point of throughput is generally found through load testing.

Load test: Continuously and steadily increase the system load, test system performance changes, find out system bottlenecks and performance inflection points. If the rps pressure mode is used, the so-called increasing system load here refers to increasing the number of requests per second.

The rps timer shown in the figure below indicates that the rps will be steadily increased to 200/s within 20s

picture

view tps

picture

The following are supporting learning materials. For friends who do [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse also accompanied me through the most difficult journey. I hope it can help you too!

Software testing interview applet

The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!

The following interview question sections are covered:

1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux

6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics

Information acquisition method:

Guess you like

Origin blog.csdn.net/IT_LanTian/article/details/132383557