info-vax@ucbvax.ARPA (03/02/85)
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.
info-vax@ucbvax.ARPA (03/02/85)
From: Chris <Pace@USC-ECLC.ARPA> Actually that is too crude a measurement for most people. It also factors in the load of the machine - which can be substantial depending on when you run it. Chris. -------