Xref: utzoo comp.dcom.modems:2517 comp.mail.uucp:1955
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!rutgers!rochester!ritcv!cci632!ccicpg!arnold!dave
From: dave@arnold.UUCP (Dave Arnold)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: UUCP g stats
Keywords: Baud Bit Byte Asynchronous Serial Line Speed
Message-ID: <190@arnold.UUCP>
Date: 24 Sep 88 21:48:58 GMT
References: <184@arnold.UUCP> <1892@van-bc.UUCP>
Organization: Home, Mission Viejo, Ca
Lines: 28

In article <1892@van-bc.UUCP>, skl@van-bc.UUCP (Samuel Lam) writes:
> In article <184@arnold.UUCP>, dave@arnold.UUCP (Dave Arnold) wrote:
> >How are you computing bandwidth utilization?
> >
> >(c * 8) / b
>       ^
> >where b = baud and c = chars. per second?
> >c taken from xferstats in /usr/spool/uucp/.Log
> 
> You probably want to multiply by (at least) 10 instead of just 8
> since the 1 start bit and 1 to 2 stop bits count here as well.

That's what I thought.  But somebody told me that you have to
multiply by 8 to compute the *TRUE* overhead, including packet
headers, retransmits, delays, timeouts, AND async overhead.
So, the question is... What do we really want to know:

How much of the 9600 baud line are we using?

or

How much of what is ACTUALLY available on the 9600 baud line
are we using?  taking into account the async overhead.

Thanks for straighting this matter out.
-- 
Dave Arnold
dave@arnold.UUCP	{cci632|uunet}!ccicpg!arnold!dave