October 15, 2009
As a means for discussing the model I will follow through an example of the model being used. To do this the needs to be an example usage scenario. In this case I have chosen to use the following:
“A banking web site has retail and corporate clients, and well as a set of automated processes that must be completed overnight in the bank’s overnight batch window. The site has a standard Java web architecture, with the batch processes being initiated using a batch process at the application server. The purpose behind the model is to examine the capacity required in the major system components, and to make ensure the ongoing capability of the host systems for the site.”
If you have followed through the performance model series (here), you will note that this is exactly the same scenario. I have chosen this in order to be able to compare and contrast the application of the performance and project estimation models. There are clear differences in approach that need to be considered. For those that like to skip to the end I have provided a copy of the final estimation example filled out here:
Estimation project estimate
April 7, 2006
When creating a system it is common knowledge that its performance is important, since users of the system will be put off it is deemed to be too slow. It is also common knowledge that performance testing tools, such as OpenSTA, can create load tests to help make sure that your system will perform. The use of these and other tools and techniques to make sure that the system as a whole performs well is, however, rather less well understood. As part of the consultancy approach that I use I have created a document that outlines an approach to fitting performance testing into a company’s development process. The document provides a context for managing system performance, and was originally written to use during consultancy assignments. I have decided to offer it as a Free Resource for those who might find it useful.
The document more describes the management approach required for the Capacity Management, rather than going into the technical details. As such, it does not assume detail technical knowledge or go into the mathematical basis for performance modelling or testing. At 18 pages it is quite short for one of my documents, and can be downloaded from: Principles of Capacity Management