[18218] in North American Network Operators' Group
Re: running summary on caching
daemon@ATHENA.MIT.EDU (Robert E. Seastrom)
Tue Jun 30 18:53:28 1998
Date: Tue, 30 Jun 1998 18:43:46 -0400 (EDT)
From: "Robert E. Seastrom" <rs@bifrost.seastrom.com>
To: peterb@ncne.org
CC: nanog@merit.edu
In-reply-to: <000e01bda432$1ccc19e0$3a3db680@haroun.psc.edu> (peterb@ncne.org)
From: "Peter Berger" <peterb@ncne.org>
It's worth noting that as pipes get bigger and faster, caching
assumes a greater, not lesser, importance. Higher bandwidth
and constant latency means a greater bandwidth-delay product,
and a corresponding degradation in performance. Caching is
just as much about local replication to reduce latency as it is
about "conserving bandwidth."
Particularly when a large proportion of the stacks out there perform
very poorly under the prevailing conditions in today's Internet with
its medium-to-high, jittery latencies and occasional to frequent
packet loss (cough, cough, Redmond, cough). Far better to use a proxy
on a platform like BSD that at least doesn't have an egg-sucking TCP
implementation.
---Rob
