Load Testing With Blazemeter

IS&T has an Enterprise Blazemeter contract is now live.  As part of the contract, we’re entitled to 5 named accounts:

istload1@mit.edu - Education Systems
istload2@mit.edu - Admin. Systems
istload3@mit.edu - Systems Engineering
istload4@mit.edu - Data Management
istload5@mit.edu - spare / O&I

They’ve also allocated us the following 10 dedicated IPs for load testing:

 54.225.93.201
 54.225.93.199
 54.225.93.195
 54.225.93.175
 54.225.93.149
 54.225.93.128
 54.225.92.250
 54.225.92.224
 54.225.92.139
 54.225.92.136

which are associated with the US-East region in the Blazemeter UI (and also with the Amazon US-East region).  We’ve added these IPs to the firewall access list for the appropriate networks in E40 so you should be able to initiate load tests against your non-production environments without needing to request any firewall access changes.

How to add the IP Address Into Your Test

Once we provide you with these IP addresses, you can set these IP addresses in the test’s advanced properties. It is important that each server that is part of the test will have an IP address.

For example, if you are using only console, you need only one IP address. If you are using one console and three engines, you will need four IP addresses.

Instructions:

 1. Under advance properties, please enable use of private IPs

 2. Please include one IP per line. Please make sure there are no extra characters such as space or tab – just the IP,

 3. The number of IP addresses should be the same as the number of servers used in the test (including console).