Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!astroatc!johnw
From: johnw@astroatc.UUCP (John F. Wardale)
Newsgroups: comp.arch
Subject: Re: Benchmark Timing
Message-ID: <276@astroatc.UUCP>
Date: Wed, 13-May-87 17:15:04 EDT
Article-I.D.: astroatc.276
Posted: Wed May 13 17:15:04 1987
Date-Received: Sat, 16-May-87 06:38:39 EDT
References: <4294@nsc.nsc.com> <28200036@ccvaxa> <1967@husc6.UUCP>
Reply-To: johnw@astroatc.UUCP (John F. Wardale)
Organization: Astronautics Technology Cntr, Madison, WI
Lines: 26

> [paraphrased:] should you use wall time, system+user time, or just
>		 user time

As a software developer who uses (almost excludively) "complete
systems" I want benchmark timings to be real (wall, or elapsed)
time.  I don't care how its distributed!  If/when I type 
"make all" (or what ever I'm working on) all that maters to me, is
how long I have to sit (and read news :-) while the make is
running.  To average out system loading, report wall time for
running it:
1) on an "empty" system
2) ten times from ten terminals
3) forking 10 parralel copies from each of 10 terminals (100 from
	100 terminals would be better, but *HARD* to do in reality)


			John W

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Name:	John F. Wardale
UUCP:	... {seismo | harvard | ihnp4} !uwvax!astroatc!johnw
arpa:   astroatc!johnw@rsch.wisc.edu
snail:	5800 Cottage Gr. Rd. ;;; Madison WI 53716
audio:	608-221-9001 eXt 110

To err is human, to really foul up world news requires the net!