Performance & Load Testing

Resources Center

Distributing load across key performance scenarios


While designing a performance test, it is extremely important to understand which of the all business scenarios the test should include. While doing so, the load subjected on and the criticality of each those scenarios need to be considered. This is not an easy job and exhaustive discussion need to happen between the business teams, the project managers and the technical teams. The exhaustive discussions and analytics data obtained from web analytics tools can lead to identification of the right scenarios to be tested. However the job doesn’t end there. Identifying the load distribution across those scenarios during the test is also a key task and needs to be performed astutely. In this blog, let’s understand how to distribute the load across different business scenarios. Following are the steps as are performed by the business teams –

Business targets:

Connect with the sales & marketing teams and understand what sells in the market. Understand the features from them as they visualize seeing in the product. Also understand the nature of other products in the market from the competitor and what performance features the competitors provide to the end users. This would help in setting the business target.

Web log information for applications which are already live:

Download the weblog data and from the same extract following key information –

  • Key business flows (from session information for individual users) performed
  • Think time values between two subsequent business transactions
  • Duration of session
  • Load values in terms of pages (or) transactions (or) users per unit load
  • User exit time (time on average that a user spends in a session)

For new websites:

  • Create a beta version of the site (if being deployed for the first time), assign it to internal team members and to some external members who could access the site and generate the web analytics data that can be used to determine the user distribution.
  • Run a sample test with this load. Create a beta version site and make it available to limited number of users who could be monitored for their activities on the site.

Your business insights:

Based on user activity data, web analytics data and your business insights, try to understand the load that can be expected on different modules (components) of the application and distribute the load accordingly.

After collating this information and finalizing the same, following are some key activities that the teams must complete so as to be compliant with the process (an overall idea presented here)

  • Once key performance business flows are determined and load distribution patterns are identified, visual models to demonstrate them to stakeholders and managers can be created.
  • The teams can target to create easy to understand business models so that those are easy to understand even to teams that are non-technical.
  • It is essential to include information related to the key data item as would be included in the test so that the dynamism of the test could also be studied using the data as presented.

Thus, these are some ideas that can be used to distribute load across key performance scenarios. It is however essential to understand that activities of end users and the load patterns may change as the product evolves and as the project changes and hence it is important to perform the above activity (of load distribution) in a repeated manner after a specific period of time so that any change in load distribution can be appropriately studied and implemented in the project. This is how one can target to take his test more close to production scenario and thus be able to perform the test as user perform their actions in production.


Learn more about QTest
AgileLoad.com
Agile Software Security


More Blog