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
- Total Users
- Duration / Iterations
- Ramp Up Time
- Ramp Up Steps
- Limit RPS
- Changing RPS Limits 'On the Fly'
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.
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.
Set the duration for the entire test, in minutes.
Or, toggle to Iterations and set the duration in iterations.
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.
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.
You can click on the Run Time Control button in the top right corner of the reports section, and then choose Change RPS to change the RPS on the fly.
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.