The locations_weighted parameter in your Taurus configuration file (yml) determines how many engines are allocated to run a test and how the Concurrency is spread over these engines.
locations-weighted: false means that the concurrency of the test is reached by starting the exact the number of machines at each location and spreading the load over these engines pro ratio.
If locations-weighted is not specified or is set to true, the amount specified for each location is only used to calculate the percentage of the concurrency to run at that location.
Examples:
1. Running 20 users using locations-weighted = false and 2 locations.
The result is 20 users running from 5 different engines: 3 from us-central1-a and
2 from us-east-1.
Each engine will run 4 virtual users, since we have 20 users divided into 5 engines.
concurrency: 20 locations: us-central1-a: 3 us-east-1: 2 locations-weighted: false
2. Running 20 users without specifying the locations-weighted field and 2 locations.
The result is 20 users running from 2 different engines: 3/5 of the users (12 users) will run from us-central1-a.
2/5 of the users (8 users) will run from us-east-1.
As BlazeMeter default value allows up to 500 virtual users per engine, this example will run 1 engine per location, and a total of 2 engines for the test.
concurrency: 20 locations: us-central1-a: 3 us-east-1: 2
3. Running 20 users without specifying the locations-weighted field and 1 location.
The result is 20 users running from 1 location.
As BlazeMeter default value allows up to 500 virtual users per engine, this example will run 1 engine per location, and a total of 1 engines for the test.
concurrency: 20 locations: us-central1-a: 3
4.Running 20 users using locations-weighted = false and 1 location.
The result is 20 users running from 2 different engines, both of them from us-central1-a.
Each engine will run 10 virtual users, since we have 20 users divided into 2 engines.
concurrency: 20 locations: us-central1-a: 2 locations-weighted: false
0 Comments