Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuxlm.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!whuxlm!jph
From: jph@whuxlm.UUCP (Holtman Jim)
Newsgroups: net.arch,net.unix-wizards
Subject: Re: IOCALL results and problems
Message-ID: <892@whuxlm.UUCP>
Date: Sat, 21-Dec-85 18:35:03 EST
Article-I.D.: whuxlm.892
Posted: Sat Dec 21 18:35:03 1985
Date-Received: Mon, 23-Dec-85 04:21:00 EST
References: <354@ncr-sd.UUCP> <457@rna.UUCP> <761@petrus.UUCP>, <335@geowhiz.UUCP> <1035@homxb.UUCP>
Organization: AT&T Bell Laboratories, Whippany
Lines: 40
Xref: watmath net.arch:2346 net.unix-wizards:16213

> Larry McVoy writes:
> >I tend to agree with Dan.  I think what people would like to see is a 
> >benchmark which measures how well Unix, running multiple users, performs
> >on each machine.  The benchmark would have to measure something that did
> >not vary widely (such as I/O devices), as those results would only reflect
> >how much one had spent on the bus & disk.  So, how about this:
> >
> >The dryhstone benchmarks are considered good tests of the CPU (at least by 
> >me they are), but don't really test Unix at all (in fact some people run 
> >them in standalone mode).  How about a version, (called forkstone?), which
> >runs the dryhstone as 1, 2, 8, and 64 concurrent processes?  This would
> >show 1) the speed of the CPU, 2) first part of the curve, 8) a nice single
> >user level, and 64) what happens when you have multiple users.  
> >
> >It would not test I/O, which is a hard thing to test fairly.  It would get
> >rid of those Z80 dryhstones (flame, flame) as they're not multi tasking...
> >
> >I guess if there is any response and nobody wants to do it, I'll hack the
> >drystones.  I think it would be better if the original author did it, as
> >{s}he probably can understand that bastardized {C}Ada source.
> 
> I don't think that running multiple dhrystones would measure anything more
> than the cost of doing a context switch once every <scheduling granularity>.
> Except on a multiple processor machine, the time will be N*1 dhrystone +
> M context switches.  There are easier ways to measure the time to do a context
> switch.  If you want to measure multi-user response, you've GOT to open the
> IO can-of-worms, since they WILL be doing IO.
> 
> Rick Richardson, PC Research, Inc. (201) 922-1134
> ..!ihnp4!houxm!castor!{rer,pcrat!rer} <--Replies to here, not to homxb!!!
> 
> P.S. Rheinhold Weicker is the author of Dhrystone.  I apologize for
> creating the bastardized {C}Ada source from his original Ada!

*** REPLACE THIS LINE WITH YOUR MESSAGE ***
Results for VAX 8600 running SVR2

1.2   Real
1.1   System
0.0   User