*BSD News Article 74487


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!psgrain!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!newshost.convex.com!news.onramp.net!zdc!zdc-e!szdc-e!news
From: "John S. Dyson" <toor@dyson.iquest.net>
Newsgroups: comp.os.linux.networking,comp.unix.bsd.netbsd.misc,comp.unix.bsd.freebsd.misc
Subject: Re: TCP latency
Date: Mon, 22 Jul 1996 19:28:42 -0500
Organization: John S. Dyson's home machine
Lines: 27
Message-ID: <31F41CBA.41C67EA6@dyson.iquest.net>
References: <4paedl$4bm@engnews2.eng.sun.com>   <4s8cuq$ljd@bertrand.ccs.carleton.ca> <31E7C0DD.41C67EA6@dyson.iquest.net>   <4s8tcn$jsh@fido.asd.sgi.com> <31E80ACA.167EB0E7@dyson.iquest.net>   <4sadde$qsv@linux.cs.helsinki.fi> <31E9E3A7.41C67EA6@dyson.iquest.net>   <4sefde$f0l@fido.asd.sgi.com> <31EBB017.167EB0E7@dyson.iquest.net>   <31EFEFE3.5282@cohprog.com> <4sp67q$1ft@uriah.heep.sax.de> <4sun9q$25u@stdismas.bogon.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0b5a (X11; U; FreeBSD 2.2-CURRENT i386)
Xref: euryale.cc.adfa.oz.au comp.os.linux.networking:46104 comp.unix.bsd.netbsd.misc:4141 comp.unix.bsd.freebsd.misc:24260

John Henders wrote:
> 
> In <4sp67q$1ft@uriah.heep.sax.de> j@uriah.heep.sax.de (J Wunsch) writes:
> 
> >Yann Stettler <stettler@cohprog.com> wrote:
> 
> >> PS : I missed the begining of the thread, can someone tell me
> >> how all this will affect the networking capacity of my 386
> >> computer connected to the internet via a 9600bps modem ?
> 
> >The beginning of the thread was a signature telling something like:
> >``Foozolix beating Barzumix today: TCP latency is 2.3 ns vs. 4.5 ns''
> 
> Well, not really. Alan's signature in fact read.
>
> 
> At this point, Steinar Haug added the freebsd group to the newsgroups line
> <4qc60n$d8m@verdi.nethelp.no>, and John Dyson followed up,
> commenting that the benchmark was meaningless
> <31D2F0C6.167EB0E7@inuxs.att.com> and the rest is history.
> 
It isn't totally meaningless, but certainly doesn't tell the whole
story.
It in itself shows only a very small part of the picture.

John