Pst … Wanna Performance Model?

May 7, 2006

A second item that I have put together for use on assignments is a “Generic Performance Model”. This model is built as a large Excel Spreadsheet (20Mb download). Using it allows examination of how system performance may vary with user demand, time and system calibration parameters. Since it is a large spreadsheet it takes a while to re-calculate when changes are made, but it does allow useful evaluation of the likely behaviour of a system. Some caution is needed in using it as the usual IT principle of “Garbage in, garbage out” applies. I will provide documentation of the various pages of the model over the next few bulletins, or please feel free to join my web site and ask questions there.

The model may be downloaded from: Generic Performance model

Please Note: The spreadsheet comes for use “as is”. If I find, or am informed about, defects I will resolve them – then  provide feedback in the forums of my web site and in the next monthly bulletin. It is, however, a complex spreadsheet which I am providing for free and so can not provide a guarantee beyond this.


How much should be spent on ensuring system performance?

May 7, 2006

The level of performance proof required of projects can fall on both sides of an optimal “cost – benefit” line for a system. If a project spends too little effort on proving performance then the result will be problems and complaints in production. If a project has overly stringent performance criteria, the result will be high costs and long delivery delays for the project. Read the rest of this entry »


From the news… SOA – the next big performance problem

April 7, 2006

It would seem that “Service Oriented Architecture” (SOA) is taking off as a technology in fashion. As usual, most of the news is generated by people wanting to sell it as the next big thing ready for the prime time. If followed as it is being sold at present, the concept is liable to lead to significant performance problems. SOA is sold on having a large number of “users” who are then often other systems. This is followed all the way back to the real users through an unknown number of tiers. The complexity of managing this sort of architecture increases significantly as the number of tiers increases. If this is then managed without due consideration for managing the system capacity and performance the result will be problems in the future. That is not to say that I don’t see a benefit in the overall technology – there is great potential. Just consider carefully how the performance of operational systems might be proven to be sufficient for the long term.


Governance of Capacity Management

April 7, 2006

In a previous employment, the employer had an operational department who were responsible for signing off the performance of a system before it was allowed in to production. Their method for doing this was working with delivery projects to make sure that the project provided sufficient evidence that the system they were delivering would perform in the long term. They would also check that the operational managers had access to appropriate mechanisms to monitor that the systems were performing according to the evidence that had been provided. When requested to do so they would provide expertise to the delivery projects in the appropriate use of capacity management techniques, but they were primarily a gate keeping and monitoring function. Read the rest of this entry »


Principles of Capacity Management

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