From: richard <richard@pacdat.net>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Failure to convince
Date: Fri, 11 Feb 2011 08:29:57 -0800 [thread overview]
Message-ID: <1297441797.29639.8.camel@amd.pacdat.net> (raw)
I had an email exchange yesterday with the top routing person at a local
ISP yesterday. Unlike my exchanges with non-tech people, this one ended
with him saying Bufferbloat was not a problem because...
"I for for one never want to see packet loss. I spent several years
working on a national US IP network, and it was nothing but complaints
from customers about 1% packet loss between two points. Network
engineers hate packet loss, because it generates so many complaints.
And packet loss punishes TCP more than deep buffers.
So I'm sure that you can find a bunch of network engineers who think
big buffers are bad. But the trend in network equipment in 2010 and
2011 has been even deeper buffers. Vendors starting shipping data
centre switches with over 700MB of buffer space. Large buffers are
needed to flatten out microbursts. But these are also intelligent
buffers."
His point about network people hating packet loss points up the problem
we'll have with educating them and the purchasing public that at least
some is necessary for TCP to function.
Not having been in charge of a major backbone recently, I have to admit
that my understanding of today's switching hardware was to be able to
deal with everything "at wire speed" with cut-through switching, unlike
the store-and-forward typical switches and routers at the consumer
level.
richard
--
Richard C. Pitt Pacific Data Capture
rcpitt@pacdat.net 604-644-9265
http://digital-rag.com www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333 57F0 4F18 AF98 9F59 DD73
next reply other threads:[~2011-02-11 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 16:29 richard [this message]
2011-02-11 16:53 ` Jim Gettys
2011-02-11 19:23 ` Richard Scheffenegger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297441797.29639.8.camel@amd.pacdat.net \
--to=richard@pacdat.net \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox