As you know that Basic Thread Group element has certain limitations, such as if you want to do a step-up load test (ramp-up the threads in bulk after a fixed delay) then you can not create such workload in the basic thread group. Concurrency Thread Group helps to design such scenario. A distributed load can be formed by using the Concurrency Thread group.
How to download “Concurrency Thread Group” plug-in?
1. Click the link to download Concurrency Thread Group Plugin
2. Unzip the folder
3. Copy the file jmeter-plugins-cmn-jmeter-<version>.jar to lib folder of Apache JMeter
apache-jmeter-<version> –>lib –> Paste jmeter-plugins-cmn-jmeter-<version>.jar
4. Copy the files jmeter-plugins-casutg-<version>.jar and jmeter-plugins-manager-<version>.jar to ext folder of Apache JMeter
apache-jmeter-<version> –>lib –>ext -> Paste jmeter-plugins-casutg-<version>.jar and jmeter-plugins-manager-<version>.jar
That’s it!
Please note .jar file version may change in case of the plug-in update.
Please note .jar file version may change in case of the plug-in update.
How to open/add “Concurrency Thread Group” in Test Plan?
1. Select "Test Plan" node
2. Right click on "Test Plan" node
3. Mouse hover "Add"
4. Mouse hover "Thread (Users)"
5. Click "bzm – Concurrency Thread Group"
How to configure Work Load using “Concurrency Thread Group”?
1. Once the Concurrency Thread Group is added in the test plan you can configure the scenario.
2. Please refer to the configuration shown below
How to remove “Concurrency Thread Group”?
1. Select "bzm – Concurrency Thread Group" node
2. Right click on "bzm – Concurrency Thread Group" node
3. Click "Remove" (Mouse) or "Delete" button from keyboard
4. Click "Yes"
What are the attributes of “Concurrency Thread Group”?
a. Name: To provide Thread Group name. It may be your Test Case/Test Scenario name
b. Comments: To provide comments
c. Action to be taken after a Sampler error: Actions taken in case of sampler error occurs, either because the sample itself failed or an assertion failed etc. The possible choices are:
i. Continue - ignore the error and continue with the test
ii. Start Next Loop - ignore the error, start next loop and continue with the test
iii. Stop Thread - current thread exits
iv. Stop Test - the entire test is stopped at the end of any current samples.
v. Stop Test Now - the entire test is stopped abruptly. Any current samplers are interrupted if possible.
d. Target Concurrency: Total number of threads (users) in the test.
e. Ramp-up Time (min): Total ramp-up duration in minutes. You can also provide ramp-up duration in seconds by choosing "seconds" in Time Unit option given below the scenario chart.
f. Ramp-up Steps Count: Total number of steps in which a group of threads (users) will ramp-up. In above example, 20 threads (users) are being activated after each 4 minutes interval (=Ramp-up Time/Ramp-up Steps Count).
g. Hold Target Rate Time (min): The steady state when all the threads are active. This is also called as system monitoring window. If you want to monitor the system/application performance for 1 hour then the value for hold target rate time will be 60 minutes or 3600 seconds. The ramp-up time does not add to this time.
h. Time Unit: To change the input time unit either in minute or in second.
i. Thread Iterations Limit: Maybe the purpose of this option to control the loop count, but unfortunately it does not work so you may keep it blank.
j. Log Thread Status into File: Provide the full path of the file along with the name where you want to save the log file. e.g. C:\PerfMatrix\Result\testLogFile.log
Arrival Thread Group
Stepping Thread Group
Related Topics:
- Thread Group
- Ultimate Thread Group
- setUp Thread Group
- tearDown Thread Group
- Arrival Thread Group
- Apache JMeter
Will the concurrency thread group work in master slave configuration?
ReplyDeleteNo
ReplyDelete