Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mailrus!ames!uakari.primate.wisc.edu!ark1!nems!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: sadp on i386
Keywords: sadp i386
Message-ID: <21823@mimsy.umd.edu>
Date: 14 Jan 90 22:44:51 GMT
References: <1583@aber-cs.UUCP> <7348@cbnewsh.ATT.COM> <18431@nuchat.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 15

In article <18431@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes:
>	when the request counter drops to zero, divide the elapsed
>	time by the serviced counter to get the average service time
>	for the session.  Merge the average into your running average
>	using the serviced counter as a weighting factor.

Beyond `some sort of statistics on some sort of controller', I have
no idea what this is all about.  However, note that the algorithm
(not quoted in entirety above) assumes that the request counter will
drop to zero.  This is a very strong probability, but is not assured;
in particular, it will lead to bizarre `continuous controller activity'
benchmarks.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris