Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Getting timings without much fuss
Message-ID: <5174@ucbvax.ARPA>
Date: Sat, 2-Mar-85 00:10:23 EST
Article-I.D.: ucbvax.5174
Posted: Sat Mar  2 00:10:23 1985
Date-Received: Sun, 3-Mar-85 03:12:49 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 33

From: maxson%vaxwrk.DEC@decwrl.ARPA  (VAXworks 223-9408)

	If you're not too fussy (and who can afford to be these days?)
	this method returns runtime for a given program.

	Create a command file of the following sort, then invoke it.

	$ASSIGN logfile.log SYS$OUTPUT
	$SHOW TIME
	$RUN ProgramBeingTested.EXE
	input line 1
	input line 2
	.
	.
	.
	input line n
	$SHOW TIME
	$DEASSIGN SYS$OUTPUT
	$EXIT

	Note that this method necessarily includes the time consumed by a
	SHOW TIME DCL command, and also includes the image activation time
	of ProgramBeingTested.EXE. If you're looking at a program with an
	anticipated runtime of 2 minutes or more, this inaccuracy can be
	discounted. Also, some inaccuracy inevitably creeps in because you're
	doing your output to a disk file rather than a tube. Depending on
	the amount of I/O and the disk in question, this could be a win or a
	loss versus real performance.

	But for my money, it's pretty darn close - and unless you're launching
	missiles or targeting a laser in your application, it should do the
	job.