General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat Paper
Date: Tue, 08 Jan 2013 13:44:46 +0100	[thread overview]
Message-ID: <87vcb7hmip.fsf@toke.dk> (raw)
In-Reply-To: <20130107175417.3b87e0ce@nehalam.linuxnetplumber.net>

[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]

Stephen Hemminger <shemminger@vyatta.com>
writes:

> The tone of the paper is a bit of "if academics don't analyze it to
> death it must not exist". The facts are interesting, but the
> interpretation ignores the human element. If human's perceive delay
> "Daddy the Internet is slow", then they will change their behavior to
> avoid the problem: "it hurts when I download, so I will do it later".

Well severe latency spikes caused by bufferbloat are relatively
transient in nature. If connections were constantly severely bloated the
internet would be unusable and the problem would probably (hopefully?)
have been spotted and fixed long ago. As far as I can tell from their
graphs, ~5% of connections to "residential" hosts exhibit added delays
of >=400 milliseconds, a delay that is certainly noticeable and would
make interactive applications (gaming, voip etc) pretty much unusable.

Now, I may be jumping to conclusions here, but I couldn't find anything
about how their samples were distributed. However, assuming the worst,
if these are 5% of all connections to all peers, each peer will have a
latency spike of at least 400 milliseconds for one second every 20
seconds (on average). Which is certainly enough to make a phone call
choppy, or get you killed in a fast-paced FPS.

It would be interesting if a large-scale test like this could flush out
how big a percentage of hosts do occasionally experience bufferbloat,
and how many never do.

-Toke

-- 
Toke Høiland-Jørgensen
toke@toke.dk

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  parent reply	other threads:[~2013-01-08 12:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 23:37 Hagen Paul Pfeifer
2013-01-08  0:33 ` Dave Taht
2013-01-08  0:40   ` David Lang
2013-01-08  2:04   ` Mark Watson
2013-01-08  2:24     ` David Lang
2013-01-09 20:08       ` Michael Richardson
2013-01-08  4:52     ` Mark Watson
2013-01-08  1:54 ` Stephen Hemminger
2013-01-08  2:15   ` Oliver Hohlfeld
2013-01-08 12:44   ` Toke Høiland-Jørgensen [this message]
2013-01-08 13:55     ` Mark Allman
2013-01-09  0:03       ` David Lang
2013-01-10 13:01         ` Mark Allman
2013-01-09 20:14       ` Michael Richardson
2013-01-09 20:19         ` Mark Allman
2013-01-09 20:31           ` Michael Richardson
2013-01-10 18:05             ` Mark Allman
2013-01-08 14:04     ` Mark Allman
2013-01-08 17:22   ` Dave Taht
2013-01-09 20:05 ` Michael Richardson
2013-01-09 20:14   ` Mark Allman
2013-01-08  7:35 [Bloat] bufferbloat paper Ingemar Johansson S
2013-01-18 22:00 ` Haiqing Jiang
2013-01-08 19:03 Hal Murray
2013-01-08 20:28 ` Jonathan Morton
2013-01-09  0:12 ` David Lang
2013-01-09  1:59   ` Mark Allman
2013-01-09  4:53     ` David Lang
2013-01-09  5:13       ` Jonathan Morton
2013-01-09  5:32       ` Mark Allman
     [not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09  3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09  5:02   ` David Lang
2013-01-18  1:23     ` grenville armitage

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=87vcb7hmip.fsf@toke.dk \
    --to=toke@toke.dk \
    --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