art@ACC.ARPA.UUCP (09/30/87)
Hey Folks, Physics won't let us go infinitely fast!!! A practical limit is probably related to distance. Lets look at the facts: TCP has a maximum window size of 65535 bytes (16 bit field). Single satellite hop is approx. 1/2 sec round trip (approx. 90 Thousand miles). Thus for satellite, max. rate is about (65535*8)/(0.5) or 1.048 Megbit/sec. Coast to Coast should be about 30 times quicker, or about 30 Megbit/sec. Of course, this is for a single TCP session, multiply for number of concurrent sessions. Art Berggreen art@acc.arpa ------
CERF@A.ISI.EDU (10/04/87)
Art, indeed, delay is the ultimate arbiter - but your figures left out the lower delay paths for smaller nets (local ones). I think we ll agree, though, that window-based schemes suffer when long delays are involved and high speeds. The source must be tolerant of very long relative delays before receiving acknowledgement so hat pacing rather than buffer acks has to be the flow control method because buffer acks come at too long delay to be an effective low control - the loop time is too long. nt
pb@idca.tds.PHILIPS.nl (Peter Brouwer) (11/09/89)
In article <8911031631.aa28210@Obelix.TWG.COM> ljm@TWG.COM (Leo J McLaughlin) writes: > >Increase TCP MSS to 1460, window size to 5840, burn any 3c500 you might find... > Is this for tcp on PC only, I could not find such a parameter in WIN/TCP (3.1) If it is there , is there any description of tunable parameters in the documentation ? -- Peter Brouwer, # Philips Telecommunications and Data Systems, NET : pb@idca.tds.philips.nl # Department SSP-P9000 Building V2, UUCP : ....!mcvax!philapd!pb # P.O.Box 245, 7300AE Apeldoorn, The Netherlands. PHONE:ext [+31] [0]55 432523, # Never underestimate the power of human stupidity