Performance analysis starts on "Day 1" of the project. There are some "rules of thumb" that can be used to start estimating the performance and to determine a "resource budget" for the components (how much can be spent to process a unit of work). There are some simple "back of the envelope" calculations that can be done (and should be continuously recalculated throughout the life of the project) that will provide targets against which the software can be tested as soon as the developer has a working copy in unit testing. This paper outlines some of the techniques that the author has found valuable in doing performance analysis for the last 35 years. There is nothing unique about these techniques, but they can be applied to all types of systems from computer systems to call centers to inventory management in a factory and to barbershops. These are techniques that everyone on the project from the system engineers to the architects to the testers should know how to use.
展开▼
