Xref: utzoo comp.dcom.modems:2579 comp.mail.uucp:2061
Path: utzoo!attcan!uunet!husc6!think!ames!ncar!noao!asuvax!nud!mcdchg!clyde!watmath!egisin
From: egisin@watmath.waterloo.edu (Eric Gisin)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: UUCP g stats
Message-ID: <21254@watmath.waterloo.edu>
Date: 3 Oct 88 14:31:30 GMT
References: <183@arnold.UUCP> <1988Sep20.184054.2403@utzoo.uucp> <184@arnold.UUCP> <201@arnold.UUCP>
Organization: U of Waterloo, Ontario
Lines: 14

In article <201@arnold.UUCP>, dave@arnold.UUCP (Dave Arnold) writes:
> I am seeing the same 400-600 cps on a direct 9600 baud link between
> a uVax and something else.  Can somebody out there tell me where the
> bottleneck on the VAX is?

Lack of CPU power mostly.
The BSD tty device drivers passes input characters one-at-a-time
to the line drivers through the line switch l_rint (receiver interrupt)
function.
The expensive calling convention on the VAX makes things worse here.

A 785 won't handle trailblazer input either,
it only gets 1100-1200 B/s on an idle system.
It can easily do output at full speed to a more modern Unix box though.