Generating Load from Multiple Regions – Load Tester 6.5
Load Tester’s cloud load generation feature includes the ability to use datacenters located in different geographical regions.
This post contains detailed steps for adding an Amazon EC2 account and for running a new test configuration. These instructions apply to Web Performance Load Tester 6.5 and earlier. For Load Tester 6.6 and up, see Generating Load from Multiple Countries – Load Tester 6.6.
Why Load Test From Multiple Regions?
Generating load from different regions enables more realistic load tests. Rather than using just local datacenters, tests can simulate traffic from all over the world rather than just local datacenters.
This feature also allows testing of specific issues. Some users, for example, may expect uneven distribution of traffic from various countries. Others may want to test how application performance varies by region.
Configuring a Cloud Account
To add and configure a new cloud account:
1. In the menu bar located at the top of load Tester application, click “Window” -> “Preferences.”
2. In the “Preferences” menu, expand the “Web Performance” entry and select “Cloud Accounts,” then click “Add.”
- After clicking “Add,” a disclaimer will appear confirming the use of Load Tester to control virtual instances on your behalf and that you accept responsibility for and any charges generated by any actions using this feature.
3. In the “Amazon EC2 Account” menu, enter a) a name for this account, b) your Amazon Access Key, c) Secret Access Key, and d) a region, then click “OK.”
- You may also add a security key. Security keys allow users to create multiple engines under one Amazon account. The engine view will only show engines created under this security key.
4. After clicking “OK,” a popup will appear prompting you to subscribe to Load Tester in your Amazon account.
5. To add another region, select an existing entry and click “Duplicate.”
The “Cloud Account” menu will appear, populated with the previously entered account information. Change the name and region to distinguish new entries.
Creating and Running a New Load Configuration
1. Open a recording.
2. In the menu located at the top of the navigator panel, select “New” -> “Load Configuration.”
3. In the “Ramp” menu, modify a) test duration, b) test plan, c) number of virtual users, and d) hold and ramp duration, then click “OK.”
4. In the “New Load Configuration” pane, select the testcase you want to edit from the dropdown menu, then click the 
symbol.
5. In the inspection pane located in the lower half of the Web Performance application, select the “Engines” tab and click “Add Engine.”
6. In the “Add Load Engine” menu, check the box labeled “Create new cloud engine(s)” and select a cloud account from the dropdown menu, then click “OK.”
7. In the “Create Cloud Engine” menu, choose the number of engines you would like to use and the engine type, then click “Create.”
8. Click 
to run a test using the new load configuration.
NOTE: Startup procedures may take several minutes, and tests will run for the preset duration or until stopped.
Stopping a Load Test
Users have several options for terminating instances:
1. At the end of a test, Load Tester will generate pop-up will appear prompting the user to terminate cloud engines.
Click “Yes” to terminate any engines still running.
2. The “Cloud Accounts” menu contains an automatic idle time termination option.
This feature will terminate any instances that have idled for a set period of time. For example, if a user runs a ten-engine test, then runs a two-engine test, Load Tester will automatically terminate the remaining eight engines after the set timeout period.
3. To terminate cloud engines at any time, except when running a Load Test, select the “Engines” tab in the inspection pane located in the lower half of the Web Performance application.
4. Select the instance you would like to terminate.
5. Then, click “Remove.”
Additionally, when closing the application, you will receive a reminder popup if you have any instances still running.
When to Terminate Instances
Amazon rounds instance charges up to the hour. For example, If you configure a test to start one engine for 10 minutes and stop it, then repeats this process two more times for additional tests, Amazon will bill 3 instance hours.
To prevent unnecessary charges, consider how many tests you plan to run before terminating instances.
If you plan to run only one test, terminate all instances upon test completion.
If you plan to run several tests back-to-back, it’s beneficial to keep engines running until completing the final test of the day.
Future Updates
Cloud load may only be generated from regions containing Amazon datacenters. We will add more datacenters to Load Tester as Amazon makes them available.