Participant geographic distribution
Each participant is launched in the location that has been specified in its configuration. These locations provided by AWS are associated with physical data centers therefore simulation is very close to a real-life scenario. The AWS locations supported by Loadero are provided in the table below.
When using Loadero's API, you can
reference the locations by the values provided in the API identifier
column.
Continent | Location | API identifier |
---|---|---|
Asia | Hong Kong | ap-east-1 |
Tokyo, Japan | ap-northeast-1 | |
Seoul, South Korea | ap-northeast-2 | |
Mumbai, India | ap-south-1 | |
Oceania | Sydney, Australia | ap-southeast-2 |
Europe | Frankfurt, Germany | eu-central-1 |
Ireland | eu-west-1 | |
Paris, France | eu-west-3 | |
North America | North Virginia, USA | us-east-1 |
Ohio, USA | us-east-2 | |
Oregon, USA | us-west-2 | |
South America | São Paulo, Brazil | sa-east-1 |
By default participants will be configured to be launched in Oregon, USA. This setting can be changed when creating or editing a participant. Instructions on how to create a participant are covered in our quickstart guide.
If you find yourself in need of generating load from a location not currently supported by Loadero, reach out to our support.
Location availability differs depending on what payment plan has been set for the project. You can find out which plans support what locations in our pricing page.
Loadero IP addresses
Loadero participants inherit the IP address from the AWS instance they are launched within. Since a single AWS instance can be running multiple participants, some of the IP addresses will be shared among participants. Loadero participants will launch from a wide range of addresses, so we cannot predict the IP address that will be used. However, we have configured a static IP address for 2 regions that you can use to whitelist that address in your firewall and run Loadero tests:
- Frankfurt, Germany:
3.123.247.135
- Ohio, USA:
3.20.19.36
Before launching a high-load test in Loadero, consider DDoS protection related risks. Since several participants can be housed in the same instance and therefore share the same IP, tests may trigger DDoS events in the application that you are testing. You may need to configure the security of your application temporarily to be compatible with Loadero.
The amount of participants housed within the same instance will be dependent on how many compute units you allocated to your participants. Higher compute unit values will result in higher dispersion.
Available compute capacity
Occasionally, you may come across a situation where you launch a test but it ends up resulting in an AWS error within a few minutes. Typically this error means either that AWS is experiencing some downtime specifically in that location or that AWS did not have enough available instances to support the amount of requested participants in that location. If you encounter such an issue, we suggest two options:
- If the location of the participant is totally irrelevant to your scenario, and the scenario allows for the participants to be scatted all across the globe, then split your needed participant count across multiple locations. E.g., if your test has one participant profile with count = 10000, then reduce that count to 2500, and create three more profiles in different locations, also with count = 2500.
- If the location of the participant is totally irrelevant to your scenario, but all participants must be in the same region, then change the location setting for your participants and then try launching the test again. It could be that there are not enough instances in one region, but there are plenty in another.
- If it is important that you launch your participants with a specific location setting, then wait about 10 minutes and try launching it again. It could be that AWS can supply the necessary amount of instances by the next attempt.
If all options fail, do not hesitate to reach out to our support by using the web chat in the lower right corner of the Loadero web application.
You will not be charged for runs that result in an AWS error.