You can run from one location or distribute across multiple locations. You can also change the default ratio of users to engines or set the engine count manually in cases where you are not using the Total Users setting.
Click within the locations drop-down to display the list of locations and make your selection.
Tip: Type a few characters to filter the list. Below, typing "asi" filters the list to Asia locations:
Multiple locations, equally weighted
You can distribute your test's Virtual Users load to multiple cloud locations by clicking the '+' button. By default, the locations will be equally weighted.
Each time you press '+' a new line will be added and the % of traffic will be re-calculated to evenly distribute the users. Here's what it looks like with four locations:
Note: There is a limit of ten locations per single test. After adding a 10th engine, the '+' button will gray out. If your test requires more than ten locations, then consider setting up a multi-test instead.
Multiple locations, unequally weighted
To use multiple locations with a custom weighted (unequal) distribution, start by adding all the locations and then make your edits in the "% of Traffic" field. While you are working on your edits, a message will display that reminds you that your numbers must add up to 100%.
BlazeMeter automatically calculates the number of engines you will need based your entry in the Total Users field. The default ratio between users and engines is configured as part of your plan. In most cases, you don't need to alter this setting and you can jump ahead to the next section.
If your test is particularly resource intensive or you are running a JMeter test with multiple thread groups, you may want to change the ratio of users to engines.
Click the number to the left of "Max Users Per an Engine" and enter a new value or drag the slider. BlazeMeter will automatically adjust the number of required Engines:
If you have "Total Users" toggled off in your Load Configuration, you'll need to set the number of engines for BlazeMeter to run your test on. The default is one, but you can increase the number to the maximum allowed by your plan. Enter a new value or drag the slider.
Use care with this setting, as the number of users your test creates will equal [users defined in your script] * [number of engines].
Note: If your test is configured to use more engines than your plan allows, you'll be met with the pop-up error "Load generators are more than account's plan limit".
If this happens, go back and check the "Total Engines" slider as pictured earlier in this article. For example, you may have intended to run a 1-engine test, but the "Total Engines" setting may have accidentally been set to 2, especially if you're running a larger number of users (over 500).