First, a brief definition of each parameter:
Number of threads: simulates the number of users
Rise Time: How long does Jmeter take to start all threads
Number of cycles: the number of times each thread executes a test case
Duration in the scheduler: duration for which the test should be performed. In this case, the value in the end time field should be ignored, and the relative end time will be calculated from the start time and duration
It is important to understand that the Ramp-up period has nothing to do with the Loop account. It is associated only with the number of threads. If there are 10 threads and a rise time of 100 seconds, then each thread will start 10 seconds after the start of the previous thread for 100 seconds to start all threads in the thread group.
Now the answer to each case of a group of questions:
Thread Group 1: # of threads:1, ramp up period:0, loop count:5, no scheduler Thread Group 2: # of threads:5, ramp up period:0, loop count:1, no scheduler Thread Group 3: # of threads:1, ramp up period:1s, loop count:5, no scheduler Thread Group 4: # of threads:5, ramp up period:5s, loop count:1, no scheduler Thread Group 5: # of threads:1, ramp up period:1s, loop count:forever, duration in scheduler:5s Thread Group 6: # of threads:5, ramp up period:5s, loop count:forever, duration in scheduler:5s
Q1. Is there a difference between thread group 1 and 2?
Thread group 1 has one thread that will repeat the same test 5 times, i.e. when one test completes the repeat of the test until the number of cycles is 5
Thread group 2 has 5 threads that will start at the same time, since the acceleration period is 0, so it must mock 5 users at the same time in the system.
Q2. How much time does it take between each cycle?
The time limit is a factor in the rise time, which is divided equally between the number of threads in the thread group. Loop is a continuous process that must continue until the number of cycles is reached. Timeout is not a term used in JMeter docs, but assuming you mean you can set it between loops using Test Action or other JMeter mechanisms if you need fine-grained control.
Q3. Is there a difference between thread groups 3, 4, 5, and 6?
Yes, all parameters are different, as described above, the behavior is different.
Q4. Should groups 3, 4, 5, and 6 take 5 seconds to complete sending all requests? Should the total number of results be 5 in each group?
No, this is all subjective for each condition. In the group of the 3rd topic, one thread must execute the same thread 5 times, therefore control over time
There are 5 threads in Thread Group 4 and based on the rise period, each thread should start 1 second after the other, so it will take at least 4-5 seconds to complete the test (after the last test)
Thread group 5 and 6 should only run for 5 seconds. If the test is completed before that, then a fine, otherwise the test must be stopped and stopped.
Q5. When I tried thread group 5, I got about 83 answers, why aren't there only 5 answers? Does this mean that the rise period is not working?
Why should there be only 5 answers ??? A group of 5 threads should create one thread, which should run the test in a loop forever. If the duration has not been determined, the test will run in an endless loop. Since the duration is determined, the test should only be performed during the duration period.
Note to all: the number of cycles depends on the flow. It determines the number of test repetitions for each thread. Rise period is associated with C # Thread (User) and is not related to the number of cycles