Browse Prior Art Database

Peformance Summary Invention

IP.com Disclosure Number: IPCOM000013742D
Original Publication Date: 2000-Dec-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 3 page(s) / 87K

Publishing Venue

IBM

Abstract

A method is disclosed for producing simple and meaningful statistical results of multi-step use cases from performance tests under simulated loads. This method has three benefits over prior art. 1. It allows a proper average performance computation of a use case under load. 2. It allows a use case two have multiple definitions for different scripts and users. 3. It allows a step to belong to multiple use cases.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

Peformance Summary Invention

A method is disclosed for producing simple and meaningful statistical results of multi-step use cases from performance tests under simulated loads. This method has three benefits over prior art.
1. It allows a proper average performance computation of a use case under load.
2. It allows a use case two have multiple definitions for different scripts and users.
3. It allows a step to belong to multiple use cases.

Prior art contains many examples where program drivers have been written to exercise server programs under simulated load of many users. These programs typically have a way of recording a script listing resources to access, and then having many virtual clients playback the script thereby putting strain on the server.

In the prior art virtual clients can be assigned roles such as expert or novice to help create a realistic mixture of users. Each role has a different script that it plays back. In the prior art virtual clients typically record the data and timing results of each access attempt and determine if the data received matches a baseline result and summarizes the information for each resource by giving minimum, maximum and average response times.

This new method groups resources together into use cases. For example making an ordered list of URLs and grouping them into a use case to check a telephone's long distance usage at a phone company's Internet Web site. This method is especially useful on web sites since the browser is a very thin client and must go back to the server for each screen of a multi-step process. What would be useful is to know how long it took on average to complete the entire use case, not just one of the steps.

The information traditionally supplied by prior art is not sufficient to compute this easily and accurately. Consider the following raw access table. It lists three exercises of a use case (Inquire on Telephone Usage). The first is by a novice that requires three screens. The other two experts require only two screens to complete the use case.

Virtual ResourceClient Time Required 1 http://domain.com/usage/step1.html 10
1 http://domain.com/help.html 10
1 http://domain.com/usage/step2.html 13
2 http://domain.com/usage/step1.html 12
2 http://domain.com/usage/step2.html 16
3 http://domain.com/usage/step1.html 14
3 http://domain.com/usage/step2.html 12

1

Page 2 of 3

In prior art a summary might have been given as in th...