[10562] in North American Network Operators' Group
Re: Keynote/Boardwatch Results
daemon@ATHENA.MIT.EDU (Craig A. Huegen)
Wed Jul 9 17:55:31 1997
Date: Wed, 9 Jul 1997 14:34:53 -0700 (PDT)
From: "Craig A. Huegen" <c-huegen@quadrunner.com>
To: "Alex.Bligh" <amb@xara.net>
cc: Jack Rickard <jack.rickard@boardwatch.com>,
Avi Freedman <freedman@netaxs.com>, mohney@access.digex.net,
nanog@merit.edu, GeneShklar@keynote.com
In-Reply-To: <199707092112.WAA09384@diamond.xara.net>
On Wed, 9 Jul 1997, Alex.Bligh wrote:
==>ones (with a given cell loss probability), and being careful to remember
==>all that good stuff at the last but one NANOG about broken client stacks,
==>and I think you might find the above is a "non measurement".
It's a rough measurement, and if you'd go so far as to assign a 20% error
margin, you'd stillsee that a web server still owns a *significant* piece
of the click-to-data time, over 50%.
I think that a 20% error margin would be fair for this, provided neither I
nor my provider was having network problems at the time. At the time,
this was intended as a rough measurement to determine how much time was
wasted in waiting for inefficient web servers.
==>I *think* (and am not sure) that if you have a proxy set up, you
==>always get the latter once you have connected to the proxy.
==>
==>Oh, and to skew the figures in the other direction, doesn't the first
==>prompt come up while the DNS lookup is being done?
Nope. You'll see "Looking up host www.website.com..." in most browsers.
(I didn't use a browser to measure this; those "web browser says" lines
were there for the reference--a lot of people ask me why it sits there a
while after saying "contacted, waiting for response".
/cah
