Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pioneer!lamaster
From: lamaster@pioneer.arpa (Hugh LaMaster)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: TCP performance limitations
Message-ID: <2922@ames.arpa>
Date: Tue, 29-Sep-87 20:36:14 EDT
Article-I.D.: ames.2922
Posted: Tue Sep 29 20:36:14 1987
Date-Received: Thu, 1-Oct-87 05:44:13 EDT
References: <8709290008.AA00477@ucbvax.Berkeley.EDU>
Sender: usenet@ames.arpa
Reply-To: lamaster@ames.UUCP (Hugh LaMaster)
Organization: NASA Ames Research Center, Moffett Field, Calif.
Lines: 28

In article <8709290008.AA00477@ucbvax.Berkeley.EDU> AUERBACH@CSL.SRI.COM (Karl Auerbach) writes:

>Someone asked me today what are the performance limits on a TCP connection.
>The situation he posited was on in which there are no intervening
:
>resources in the hosts, and low noise.  It was further posited that

An interesting question. It depends on HOW low noise your connection is.
Because of acknowledgement and retransmission requirements, the faster the
link, the lower noise it has to be to maintain a high delivered fraction of
the raw channel speed.  This is in addition to the question of the interaction
of acknowledgement delay and window size, which some have mentioned, and which
is also a big problem.  To realize the high bandwidth in practice requires
host software smart enough to adaptively distinguish between a high bandwidth
low noise channel, and something like Arpanet, and adjust its behavior
appropriately to either situation.  Offhand, I am not sure how to do this.
Anybody have any ideas?





  Hugh LaMaster, m/s 233-9,  UUCP {topaz,lll-crg,ucbvax}!
  NASA Ames Research Center                ames!pioneer!lamaster
  Moffett Field, CA 94035    ARPA lamaster@ames-pioneer.arpa
  Phone:  (415)694-6117      ARPA lamaster@pioneer.arc.nasa.gov

(Disclaimer: "All opinions solely the author's responsibility")