Xref: utzoo comp.dcom.modems:2630 comp.mail.uucp:2117
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!wasatch!utah-gr!uplherc!sp7040!obie!wes
From: wes@obie.UUCP (Barnacle Wes)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: UUCP g stats
Summary: Bottleneck on MicroVAX?
Message-ID: <209@obie.UUCP>
Date: 7 Oct 88 03:45:13 GMT
References: <183@arnold.UUCP> <1988Sep20.184054.2403@utzoo.uucp> <184@arnold.UUCP> <201@arnold.UUCP>
Organization: the Well of Souls
Lines: 21

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?

Sure.  VMS.  No joking - it spends a lot of time making sure that you
are to be allowed to read that character, this adds a lot of overhead.

> P.S. Explain how I can be getting 120 CPS on a 1200 baud line.

Easy.  VMS can verify that you are allowed to read that character and
still keep up with 1200 baud communications.  You'll probably get about
240 cps out of a 2400 baud line, too.  I don't think you'll get 480 out
of a 4800 baud line, however.  If you want more detail, ask
terry@wsccs.UUCP - he can tell you more than you ever wanted to know
about how much VMS slows character i/o on a MicroVAX II :-).
-- 
                     {hpda, uwmcsd1}!sp7040!obie!wes

         "How do you make the boat go when there's no wind?"
                                 -- Me --