How To Configure Ultimate Thread Group In JMeter?

Generic Thread Group component alongside setUp Thread Group and tearDown Thread Group stops as a matter of course with Apache JMeter group. These Ultimate Thread Group components in JMeter have certain restrictions like you can not take the responsibility model for a spike test or step-up test utilizing these fundamental thread gatherings. 

To defeat this issue and support various sorts of execution tests, some outside modules are accessible which give the alternative to make the ideal responsibility and accomplish the presentation objective. JMeter Ultimate Thread Group module is one of the outer modules which is utilized to plan the spike test type, responsibility model. Utilizing Ultimate Thread Group you can apply contingent burden on the server. 

A thread group in JMeter is the base component (parent) required in each test plan. It’s a get-together of threads executing a similar situation. There are numerous thread bunches accessible which we arrange in different manners to precisely recreate how clients collaborate with an application, how the heap is kept up, and throughout what timeframes. These settings get from what the application customers need from the heap tests, information from the investigation, and the presence of mind testing stuff. The most recent JMeter refreshes and modules accompanied a couple of fresh out-of-the-plastic new thread gatherings.

A wide range of thread bunches have a typical choice which is the ‘Move to be made after a Sampler mistake’ which is practically simple — it very well may be to proceed with the thread, start the following cycle, stop the current thread, stop the whole test or power stop the test and every single continuous thread.

Configure JMeter 

Configure JMeter 

Follow the steps referenced below to configure JMeter

1. Click on the given link. This will help you to download JMeter Plugin- JMeterPlugins-0.5.4.zip 

2. Unzip the folder. Further copy the JmeterPlugins.jar file.

3. Open the JMeter folder and go to apache-JMeter-2.8 – >lib – > ext – > Paste the record JmeterPlugin.jar inside the ext folder. 

4. Now open JMeter. Right-click on the Test Plan. 

5. Go to Add – > Threads (Users) – > jp@gc – Ultimate Thread Group 

Also read: 6 Benefits Of Testing Cloud Applications With Jmeter

Adding Ultimate Thread Group in JMeter

1. Open JMeter and right-click on the Test Plan. 

2. Right Click on Test Plan > Add > Threads(Users) > jp@gc Ultimate Thread Group. 

You can see more choices added to the list like: “bzm – Arrivals Thread Group”, “bzm – Concurrency Thread Group”, “bzm – Free from Arrivals Thread Group”, “jp@gc Stepping Thread Group” and “jp@gc Ultimate Thread Group”. 

Features of Ultimate Thread Group in JMeter

The following are the configurations settings you can see under the Ultimate Thread Group window: 

– Action has to be performed after a Sampler hits a blunder 

– Thread Schedule 

– Elapsed Time Vs Number of Active Threads Graph 

Action is Performed Only After a Sampler Error Has Been Caused 

As the name infers, this choice instructs JMeter if the execution hits a mistake due to a sampler error. JMeter gives you 5 decisions to deal with the disappointment of a sampler, and they are “Continue”, “Start Next Thread Loop”, “Stop Thread”, “Stop Test” and “Stop Test Now”. 

As a matter of course “Proceed” choice is chosen. Presently how about we take a look at the meaning of these choices. 

– Continue: JMeter will overlook the error, proceed with the execution, and the just-influenced sampler gets fizzled in the audience. 

– Start Next Thread Loop: JMeter will overlook the blunder and proceed with the execution of the next thread circle. 

– Stop Thread: Execution of the current Thread will be quit, remaining threads will be executed as characterized. 

– Stop Test: Entire Test execution will be halted if any sampler hits an error. 

– Stop Test Now: Test execution will be halted suddenly and all right now dynamic samplers will be hindered to end the execution. 

Thread Schedule 

Ultimate Thread Group in JMeter gives an exceptionally fascinating approach to planning your thread exercises. You can see a table with segments: “Start Thread Count”, “Beginning Delay, sec”, “Startup Time, sec”, “Hold Load For, sec” and “Closure Time”. Likewise, there are catches beneath the table to “Add Row”, “Duplicate Row” and “Erase Row”. We should comprehend the meaning of each field and their utilization progressively execution. 

– Start Thread Count: Here we can characterize the measure of threads to stack in a single set. The thread will begin individually until it arrives at the tally characterized per line. Suppose we have characterized 20 Thread Count in the first column then we will stack 20 clients first.

– Initial Delay, Sec: This time chooses after how long we need to hit the server interestingly. 

– Startup Time, Sec: This fills in as a Ramp-up an ideal opportunity for threads to hit the server. Start-Up Time is split between each user(Start Thread Count/Startup Time). So if we have characterized Start Thread tally = 50 and Startup Time = 10 that implies we are giving 5 seconds for each thread to hit the server. This design is material for a single line. 

– Hold Load For, sec: After every one of the threads is enacted from the single line, JMeter will hold the load up to characterized seconds. 

– Shutdown Time: After the Hold Load time-frame is finished, JMeter will close every one of the threads within a characterized closure time. 

– Add Row/Copy Row/Delete Row: To add, eliminate openings of Thread arrangement. Here, each row is a different space. 

Example: 

– As you can see in the above picture we have added 3 rows with Thread considering 10, 20, and 30. 

– Initial deferral for each of the 3 lines is kept the same as 10 seconds. 

– So after the commencement of execution, JMeter will trust that 10 seconds will send the first thread to the server. 

– Startup Time is the same as 10 seconds. Consequently, within 10 seconds every one of the 60 Users will be shipped off the server. 

– Now Hold Load Time is diverse for each column: 50, 100, and 150 seconds. So following 50 seconds of Startup time, we will have a Ramp down of threads characterized in the first line. As should be obvious, we are getting our first slope down at 1.10 mins (10+10+50 secs). 

– Similarly, other Ramp-downs will happen according to the characterized arrangement. 

Conclusion

With the utilization of Ultimate Thread Group in JMeter, you can assume full responsibility for your presentation test execution by arranging an endless number of timetable records and separate increase time, closure time, flight time for each timetable record. You can create an assortment of load patterns depending on your prerequisite and arrange a wonderful Spike Test.

Also read: 10 Most Popular Jmeter Plugin Manager