home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!noc.near.net!vaxeline.ftp.com!cream.ftp.com!jbvb
- From: jbvb@vax.ftp.com (James B. VanBokkelen)
- Subject: Re: Why would a Sun take 1.5 seconds to retransmit a missed packet?
- Message-ID: <930108124846@cream.ftp.com>
- Nntp-Software: PC/TCP NNTP
- Keywords: TCP retransmit
- Lines: 19
- Sender: root@vaxeline.ftp.com (vaxeline.ftp.com root account)
- Nntp-Posting-Host: whipped-cream.ftp.com
- Reply-To: jbvb@ftp.com
- Organization: FTP Software, Inc., Wakefield, MA
- References: <184841@pyramid.pyramid.com>
- Distribution: na
- Date: Fri, 08 Jan 1993 12:48:46
-
- In article <184841@pyramid.pyramid.com> lstowell@pyrnova.mis.pyramid.com (Lon Stowell) writes:
-
- In article <BARNETT.93Jan7091846@grymoire.crd.ge.com> barnett@crdgw1.ge.com writes:
-
- >Packets are missed by the archive system, so the Sun has to retransmit
- >the missed packets. I have noticed large delays (0.5 - 1.5 seconds)
-
- Those are pretty typical numbers for TCP layer time-outs...
-
- If so, it indicates that 1) the path is long, 2) the archive system is very
- slow or 3) the sending TCP has an inferior or broken adaptive retransmit
- algorithm. TCP should retransmit in something on the order of twice the
- average Round Trip Time (from send to ack). Some implementations use exactly
- 2X, others combine the RTT and its standard deviation. With the TCP in PC/TCP
- for DOS on a local LAN, the retransmit timeout is typically near its floor of
- 166 Ms, and I don't see any significant number of unwarranted retransmits.
-
- James B. VanBokkelen 2 High St., North Andover, MA 01845
- FTP Software Inc. voice: (508) 685-4000 fax: (508) 794-4488
-
-