Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ptsfa!ihnp4!houxm!homxb!gemini
From: gemini@homxb.UUCP
Newsgroups: comp.arch
Subject: Re: 01/31/87 Dhrystone Results and Source
Message-ID: <2387@homxb.UUCP>
Date: Sat, 14-Feb-87 17:49:23 EST
Article-I.D.: homxb.2387
Posted: Sat Feb 14 17:49:23 1987
Date-Received: Sun, 15-Feb-87 08:14:36 EST
References: <2348@homxb.UUCP> <15203@onfcanim.UUCP> <293@ames.UUCP> <1224@husc6.UUCP>
Organization: PC Research, Inc.
Lines: 16
Keywords: Benchmark, performance measurement
Summary: Predictor of other benchmarks

In article <1224@husc6.UUCP>, reiter@endor.harvard.edu (Ehud Reiter) writes:
> Has anyone actually tried to evaluate the Dhrystone (and other benchmarks)
> by seeing how well it predicts performance on real applications?  It would
> seem straightforward to take ten random applications running on specific test
> data, measure their performance on some target machine/compiler combinations,
> and statistically analyze how much of the peformance differences had been
> predicted by the Dhrystone figures.

Since Dhrystone does no I/O during the benchmark, I doubt that Dhrystone
predicts performance of *ANY* application.  Except perhaps other integer
benchmarks!  It's probably useful in predicting the performance of,
say, qsort(3), UNIX's in core sort routine, and stuff like that.  We've
found it most useful in evaluating compiler code generation technology.

Rick Richardson, PC Research, Inc. (201) 922-1134, (201) 834-1378 @ AT&T-CP
..!ihnp4!castor!{rer,pcrat!rer} <--Replies to here, not to homxb!gemini, please.