BlazeMeter is designed to speed the iterative process of testing. Frequently changed parameters can be controlled (overridden) from within the BlazeMeter UI or API, eliminating the need to edit hard-coded values in your scripts and re-upload them between tests.

• Setting Overrides
• Disabling Overrides
• Total Users
• Duration / Iterations
• Ramp Up Time
• Ramp Up Steps
• Limit RPS
• Changing RPS Limits 'On the Fly'

Setting Overrides

In the Load Configuration section, you may override the number of users, test duration and ramp up. You can also choose to turn off any of these overrides, allowing the script values to retain control. In order to do so, turn off the toggle switch in front of any parameter.

Enter numbers into the fields or use the drop-down to choose popular configurations.

Disabling Overrides

If you do not want to use any overrides, instead relying on the configuration in your original script, you can disable any and all overrides.  Simply click the toggle icon for each override you wish to disable.  Toggled right (and blue) is enabled:

Toggled left (and gray) is disabled:

Once an override is disabled, it's slider bar and number field will be grayed out, meaning it will not be applied.

To disable all overrides, simply ensure all toggles are set to the left (gray).

Total Users

Select the number of users you want deployed at the peak of your test.  BlazeMeter will divide this user population across the number of test engines deployed.

Note: If your script uses multiple thread groups, the following will apply:

• If each thread group in the script is configured for 1 user (the default setting) in the"Number of Threads (users)" field, then Blazemeter will divide the total users evenly across the thread groups, rounding up and down as needed.  For example, if you specify 10 users for 2 thread groups, each thread group will run 5 users.  If you specify 6 users for 3 thread groups, each will run 2.  If you run 11 users for 3 thread groups, Blazemeter will round up (from 3.66...) and each will run 4.  If you run 7 users for 3 thread groups, Blazemeter will round down (from 2.33...) and each will run 2.
• If you specified different user numbers for each of your multiple thread groups, then BlazeMeter will maintain the ratio of threads between the thread groups in the JMX to achieve the total users you specify here. For example, if your JMX has three thread groups and the "Number of Threads (users)" field in each of them is set to 5, 3 and 2 respectively, then a test with 1000 users specified in Load Configuration will run 500, 300 and 200 threads through those thread groups.

Duration / Iterations

You can configure your test to either run for a specified duration or for a specified number of iterations by toggling between these two options:

1. Set the duration for the entire test, in minutes.  The test will run infinite iterations until the duration is met.
2. Toggle to Iterations and set the number of iterations instead.  The test will run however long is required to complete all iterations.

CAUTION: There are some limitations to be aware of in regard to duration/iterations:

• You cannot run a test with a duration longer than your plan's limit.
• If you configure a high-iteration test using the Overrides pictured above, Blazemeter will apply a default duration of approximately 1 hour, 10 minutes. This safeguard is to prevent abuse of the system by running an infinite-duration test.  If you need to run a high-iterations test that will exceed an hour in duration, we therefore recommend disabling overrides and setting desired values directly in your script, in which case it will be allowed to run through all iterations to completion.
• If you disable overrides and have infinite iterations (loops) set in your script, make sure you set a duration in your script.  For example, if you configure a JMeter test to run infinite loops with no duration, Blazemeter will apply a 10-second duration to it instead.  This is likewise to prevent abuse of the system by running an infinite-duration test.
• You cannot configure duration and iterations at the same time in the Overrides, but if you disable all overrides, it's possible to configure both in your script itself (JMeter, for example, allows this).  If this is the case, the test will run until whichever limit -- iterations or duration -- is met first.

If you find that your test terminated before running its full duration, check for the above limitations first.

If executing a JMeter test, you can download the artifacts.zip file from the Logs Report, inside of which you will find a modified_{your_script_name).jmx file. If you open that modified JMX in your local JMeter, you can then see any thread group overrides that Blazemeter may have applied to your script.

Ramp Up Time

Select how fast you want the test to ramp-up.  This is the elapsed time in minutes from test start until all users are running.

Ramp Up Steps

Select the number of steps for the ramp-up of your test.

• The default value is to 0, which delivers a linear Ramp-up from test start until the end of Ramp up Time:
• A value of 5 delivers 20% of the peak users at start and reaches 100% at start of 5th step:

Limit RPS

This setting allows you to impose a maximum requests per second (RPS).  When you use this setting, you will see a "Change RPS" button on your live test reports and can make changes mid-test.

A dialog box will appear which lets you change the value. Set the value and click "Apply" to send the new value to the test engines.

Jump to next section:

• Load Distribution

NTC Feedback?  Bug to report?

If you have feedback about our New Test Create features or would like to submit a bug report, please send an email to support@blazemeter.com - thanks in advance!