JMeter assembly point technology and logic controller

How can we achieve real concurrency

Concurrent ： It refers to the users who are operating business in the system , stay Jemeter in , It is called the number of threads

Jemeter Each thread in the （ user ） There is a certain randomness in the sequence of business operations

Jemeter Timer

Timer： Configuration element

Used to set the waiting time between operations , Waiting time is a common control client in performance testing QPS The means of .

usage ： The timer is in each sampler（ Sampler ） Previously executed , Not after . No matter where the timer is sampler after , Or below , He's all there samp It was implemented before .

Timers are scoped ： When executing a samp Before , All timers in the current scope will be executed ;

If you want the timer to apply only to one of the current sampler, The timer is added as a child node .

Jemeter Common timers

Synchro timer Synchronizing Timer --- Marshal Point （ Used in concurrency ）

    Set a certain number of threads / Users submit requests at the same time

Pictured ,3 Requests as a concurrent , stay 3 Send it in seconds , If 3 Not enough in seconds 3 individual , It doesn't matter

Fixed timer Constant Timer -- Thinking time

  Fixed waiting time

The interval between each request is fixed

Jemeter Common logic controller

It can exist anywhere under the thread group ：

The elements of the controller type contain two types of elements ：

      A controller for the logical sequence in which the sampler sends requests in the null test plan ：

            Only once the controller 、 Circulation controller 、 Conversion controller 、If Controller etc. .

      Used to organize and control sampler nodes

          Transaction Controller、Throughput Controller etc. .

Only once the controller ：

1、 During the execution of the test plan , The child nodes under the once only controller execute each thread only once

2、 This controller is often used in login scenarios .