-
Archives
- April 2019
- January 2019
- June 2018
- January 2018
- July 2017
- April 2017
- December 2016
- August 2016
- February 2016
- September 2015
- April 2015
- February 2015
- September 2014
- February 2014
- January 2014
- December 2013
- November 2013
- July 2013
- June 2013
- March 2013
- February 2013
- January 2013
- October 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- May 2011
- April 2011
- March 2011
- February 2011
- September 2010
-
Meta
Monthly Archives: April 2017
Testing of a website behind a load balancer
When you plan a load test, one of the first things you need to know about the backend configuration is if it includes a load balancer. This is important because most load balancers distribute new user sessions by the client IP address. Some of them allow changing the distribution method. However this may be achievable only by a significant configuration change. You will hardly persuade the site admins to make such changes in the production environment.
What is a bit embarrassing in this respect is that even if you select the “distribute to the least loaded” option in LB settings, this may still mean that it will use this rule only for new IPs. After the initial connect, each IP is remembered for a certain time (from 1 hour to few days) and all new connections from the same IP will be directed to the same web server.
This creates a very big problem for load testing. If you use WAPT Pro, or any other efficient load testing tool, by default all your virtual users will share the same IP address and will be directed to the same web server behind the LB. As a result, you will not be able to test the whole system correctly. Continue reading