The process of identifying one or more composite application usage profiles for use in performance testing is known as “Workload Modeling”. Workload modeling can be accomplished in any number of ways, but to varying degrees the following activities are conducted, either explicitly or implicitly.
- Identify the objectives
- Indentify key usage scenarios. You may use the following limiting heuristics useful
- Include contractually obligated usage scenarios
- Include usage scenarios implied or mandated by performance testing goals and objectives
- Include most common usage scenarios
- Include business – critical usage scenarios
- Include performance intensive usage scenarios
- Include usage scenarios of technical concern, stakeholder concern & high visibility usage scenario
- Determine navigation paths for key scenarios
- Identify the user paths within your web applications that are expected to have significant performance impact and that accomplish one or more of the identified key scenarios.
- Determine individual user data and variances
- No matter how accurate the model representing navigation paths and usage scenarios is, it is not complete without accounting for the data used by and the variances associated with individual users. So spare some thoughts on – website metrics in web logs for usage sessions per period, session duration, page request distribution, interaction speed etc
- Determine the relative distribution of scenarios
- Identify target load levels
- Benchmark – compare with industry standard
- Baseline – create a new value for self use
- Prepare to implement the model
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
Get Free Email Updates to your Inbox!
