Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!reed!omen!caf
From: caf@omen.UUCP
Newsgroups: comp.unix.xenix
Subject: Re: Adding ports to SCO XENIX system
Message-ID: <608@omen.UUCP>
Date: Thu, 22-Oct-87 18:23:23 EST
Article-I.D.: omen.608
Posted: Thu Oct 22 18:23:23 1987
Date-Received: Sun, 25-Oct-87 06:09:12 EST
References: <94@sda.atexrd.UUCP> <787@ssc.UUCP> <7433@dartvax.UUCP>
Reply-To: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Organization: Omen Technology Inc, Portland Oregon
Lines: 15
Keywords: ports SCO XENIX

In article <7433@dartvax.UUCP> cmi@dartvax.UUCP (Theo Pozzy/R. Green) writes:
:We've pounded on it by using our software, MLINK, to do 9600 baud
:file transfers with one port looped back into another, with two
:loops running at once!

A loopback test such as this is not necessarily a good prediction of real
world performance because the loopback configuration tends to regulate
the flow of data.  The result is an implicit, unexpected flow control.

A project I was involved with some years ago folded because the company
accepted a vendor's loopback test as a valid predictor of the system's
ability to accomodate incoming data, instead of allowing me to test the
system myself before committing to it.  Needless to say, the system could
not handle anywhere near the required input throughput when connected to
other computers.