Evaluating computers and other systems is difficult for a couple of reasons. First, the goal of evaluation is typically ill-defined: customers, sometimes even designers, either don't know or can't specify exactly what result they expect. Often, they don't specify the architectural variants to consider, and often the metrics and workload they expect you to use are ill-defined. Second, they rarely clarify which kind of model and evaluation method best suit the evaluation problem. These problems have consequences. For one thing, the decision-maker may not trust the evaluation. For another, poor planning means the evaluation cannot be reproduced if any of the parameters are changed slightly. Finally, the evaluation documentation is usually inadequate, and so some time after the evaluation you might ask yourself, how did I come to that conclusion? An approach developed at Siemens makes decisions explicit and the process reproducible.
[1]
Philip Heidelberger,et al.
Computer Performance Evaluation Methodology
,
1984,
IEEE Transactions on Computers.
[2]
Giuseppe Serazzi,et al.
Workload characterization: a survey
,
1993,
Proc. IEEE.
[3]
Reinhold Weicker,et al.
An overview of common benchmarks
,
1990,
Computer.
[4]
Ray Jain,et al.
The art of computer systems performance analysis - techniques for experimental design, measurement, simulation, and modeling
,
1991,
Wiley professional computing.