Configure an Ultimate Thread Group Scenario

A thread group represents a set of threads and provides a mechanism for collecting multiple threads and executing them all at once. When using a standard Thread Group, BlazeMeter overrides the Thread Group configuration of Threads, Iterations, Ramp-up and Duration. That is not the case when using an Ultimate or Concurrency Thread Group. For your scenario to work with the Ultimate or Concurrency Thread Groups, configure the BlazeMeter test as described in this article.

Restriction: The Stepping Thread Group plugin is deprecated, use ConcurrencyThreadGroup instead.

• Configure an Ultimate Thread Group Scenario
• Configure Engines in Multiple Engines Scenario

Configure an Ultimate Thread Group Scenario

Follow these steps:

1. Upload your JMeter script to the test.
2. In the test Configuration tab, Load Configuration section, toggle off the following options:
   • Total Users
   • Duration/Iterations
   • Ramp up Time
   • Limit RPS
   • Ramp up Steps

Configure Engines in a Multiple Engines Scenario

If you run a multiple engines test, you must adjust the Threads values in your Ultimate or Concurrency Thread Group.

Example:

You are running a multiple engines test with 2000 Concurrent Users using five load engines. Then you need to adjust the Threads values to one fifth of their current values. Set the Ultimate or Concurrency Thread Group to load up to 400 threads. Otherwise, each engine runs 2000 threads. It would result in the crash of the engines or massive overload on your app server side.

Follow these steps:

1. Click the current configured number of engines.

   

   A pop-up window shows.

2. Configure the desired number of engines.
   

3. Click anywhere outside of the pop-up window.

   

   The number of engines configured is updated.