The effect of thread group on SAMPLER and loop controller in JMETER

Jmeter scripts recorded from Badboy will have a default loop controller when imported into Jmeter;

Insert picture description here

At this time, the loop controller acts on the Sampler below. At this time, we set up the Thread Group scenario as follows:
Insert picture description here
At this time, we run and check the Sampler in the aggregate report;
Insert picture description here
we find that each HTTP request is only sent 10 times, a total of 20 times, instead of the scenario we requested [10 thread groups, each loop 5 times, a total of 50 requests], the reason is that there is a logic controller

For example, in the loop controller in this scenario, the total number of Sampler requests is determined by the number of thread groups and the number of cycles of the logic controller. We modify it as follows, enter 5 in the loop controller, and run the script again after emptying it:
Insert picture description here
View the aggregate report at this time:
Insert picture description here
This also verifies that we must use the logic controller to help us set the scene when we perform the performance test and pressure test logic;

Guess you like

Origin blog.csdn.net/Love_Polaris/article/details/99739680