home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!paladin.american.edu!howland.reston.ans.net!spool.mu.edu!uwm.edu!ogicse!verdix!mark
- From: mark@verdix.com (Mark Lundquist)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: Why would a Sun take 1.5 seconds to retransmit a missed packet?
- Keywords: TCP retransmit
- Message-ID: <9517@verdix.verdix.com>
- Date: 11 Jan 93 23:01:07 GMT
- Article-I.D.: verdix.9517
- References: <184841@pyramid.pyramid.com> <930108124846@cream.ftp.com>
- Distribution: na
- Organization: Verdix Western Operations, Aloha OR
- Lines: 18
-
- In article <930108124846@cream.ftp.com> jbvb@ftp.com writes:
- >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).
-
-
- The granularity of the per-TCB timers (retransmit, RTT, etc.) on
- BSD-derived systems is 500ms.
-