Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!csus.edu!ucdavis!ucbvax!pasteur!galileo.berkeley.edu!jbuck
From: jbuck@galileo.berkeley.edu (Joe Buck)
Newsgroups: comp.arch
Subject: Re: Computers for users not programmers
Message-ID: <10857@pasteur.Berkeley.EDU>
Date: 7 Feb 91 01:10:18 GMT
References: <27A84C5C.24EF@tct.uucp> <13615@lanl.gov> <27AF17B9.72E2@tct.uucp> <5275@mentor.cc.purdue.edu> <977@TALOS.UUCP>
Sender: news@pasteur.Berkeley.EDU
Reply-To: jbuck@galileo.berkeley.edu (Joe Buck)
Lines: 15

In article <977@TALOS.UUCP>, jerry@TALOS.UUCP (Jerry Gitomer) writes:
|> Having worked for a couple of hardware vendors I can attest
|> to the fact that benchmark performance considerations biased
|> the design of some or our systems.

I certainly hope so.  What else would you want to base your designs
on other than on quantitative data on how different decisions
affect performance?  Assuming you have a well-designed benchmark
suite, of course, and your benchmark programs are real -- that is,
they accept data and produce output, without dummy loops that can
be optimized away or fakery designed to defeat optimizing compilers.

--
Joe Buck
jbuck@galileo.berkeley.edu	 {uunet,ucbvax}!galileo.berkeley.edu!jbuck