Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!HAMLET.CALTECH.EDU!zar%Xhmeia.Caltech.Edu
From: zar%Xhmeia.Caltech.Edu@HAMLET.CALTECH.EDU
Newsgroups: mod.computers.vax
Subject: Response Time Measure
Message-ID: <8605210649.AA18785@ucbvax.Berkeley.EDU>
Date: Thu, 15-May-86 14:44:43 EDT
Article-I.D.: ucbvax.8605210649.AA18785
Posted: Thu May 15 14:44:43 1986
Date-Received: Thu, 22-May-86 01:24:08 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 10
Approved: info-vax@sri-kl.arpa

[flame if you must]
My opinion of a good measure of overall load is to make a daemon perform
a simple 30 second (empty VAX) calculation and time the calculation
elapsed time over 1 min, 5 min, and 15 min. This would seem to be a better
judge of load than indicating # of processes demanding CPU (in COM state).
We have lots of batch jobs, and LAVDRIVER is totally ridiculous for
determining load (it doesn't start getting sluggish on my VAX until LAV
reports numbers above 10). Comments?
					FTG
					Zar