bzm - Arrivals Thread Group Thread Group
a "reach" is the beginning of a thread iteration (an iteration of virtual users start).
In the timetable for reaching the thread group "to reach." "To" is another method of scheduling described load. As the "arrival" is the beginning of a script iteration, iteration is therefore scheduled arrival of the scheduled start. The free-form reaches the thread group similar to thread group arrived with one major difference - more flexible scheduling.
bzm - Arrivals Thread Group (arriving thread group) is very suitable for more traditional load testing. Likely scenario might be "good when the system has 100 orders per minute, our system is operating?."
1: use our platform to design a login access request
2: Add the constant timer request the following
3: Add some listeners, such as polymerization report, throughput, number of active threads, response time, point
hit rate, etc.
using the thread group Arrivals load:
when all iterations are beginning user, JMeter will automatically create a new thread based on pressure, and therefore may produce
a large number of threads and resulting in "Out of memory", you can use the Concurrency limit field to limit the maximum number of threads.
Target arrival arrival rate :( / min): 120
Acceleration Time (minutes): 1, the time of the primary thread, where 1 minute to 120 and runs concurrently comprises duration.
Step (acceleration times): 2, the number of concurrent users is divided into steps, where concurrent thread 120 is divided into 2 steps, each step 60.
maintain the target arrival rate (minutes): 2, the thread continues to run 2 to 120 minutes
reach the target number of iterations defined target load starting within one minute. We set to 12 (0 per minute per
sec 2).
Acceleration time: defines the time to reach the target load levels.
Stepper: To define the number of goals load level
to maintain the target reach time: define the target load level duration. Here we have two choices: minutes or
seconds.
Thread Iterations Limit is defined as the number of iterations for each virtual user is running. A description of each field is blank with a
user unlimited iterations will run until the end of the test plan.
Adjust timer
timer as user think time. In milliseconds
Listener --jp @ gc - Active Threads Over Time
stepped pressing thread group needs and Active Threads Over Time (number of active at different times
the amount shown) combined, this can see the dynamic pressure effect of the step
120 where the thread only require a concurrent users can be.
