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.
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.
Enter numbers into the fields or use the drop-down to choose popular configurations.
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.
- For JMeter scripts with multiple thread groups, please note that the Total Users number will be applied to each thread group. Example: four thread groups and setting of 1,000 Total Users will deploy 4,000 users. In this case, you may need to Change the ratio of users to engines.
Duration (in minutes) / Iterations
Set the duration for the entire test, in minutes.
Note: a later release of the beta will allow toggling this setting between Duration and Iterations, to use the latter as the criteria for ending your test. Iterations is not currently supported in the beta.
Ramp up Time (in seconds)
Select how fast you want the test to ramp-up. This is the elapsed time in seconds 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:
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.