Xref: utzoo news.sysadmin:2539 comp.dcom.modems:4102 comp.unix.questions:14747
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!cs.utexas.edu!uunet!opel!johnk
From: johnk@opel.UUCP (John Kennedy)
Newsgroups: news.sysadmin,comp.dcom.modems,comp.unix.questions
Subject: Re: How to speed up uucp with Telebits(only getting 800 chars/sec )
Message-ID: <141@opel.UUCP>
Date: 7 Jul 89 12:32:10 GMT
References: <200038@hrc.UUCP> <1160@intercon.UUCP>
Reply-To: johnk@opel.UUCP (John Kennedy)
Organization: Second Source, Inc., Annapolis, MD
Lines: 24

In article <1160@intercon.UUCP> amanda@intercon.uu.net (Amanda Walker) writes:
amanda>In article <200038@hrc.UUCP>, dan@hrc.UUCP (Dan Troxel) writes:
dan> I feed several sites here in Arizona. Most of my sites get at least
dan> 1100 chars/second. But there are 2 that are getting 800-900 chars/second.
dan> 
dan> Of course, we are running Telebits, and don't have uucp source code.
dan> 

amanda> My guess is that the two sites in question are talking to their
amanda> Telebits at 9600 baud instead of 19200 baud, thus causing a bottleneck
amanda> on their end.  Either that or they're using T1000s, which only go up to
amanda> 9600.

Is it possible to tell if a given site (including your own) is suffering
from a high amount of retried data due to UART overruns, etc.?  All I've
ever seen is a *net* throughput in chars/second, but can you monitor
a success ratio on the protocol?



-- 
John Kennedy                     johnk@opel.UUCP
Second Source, Inc.
Annapolis, MD