General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mark Allman <mallman@icir.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat Paper
Date: Tue, 08 Jan 2013 09:04:45 -0500	[thread overview]
Message-ID: <20130108140445.E493059FB7F@lawyers.icir.org> (raw)
In-Reply-To: <87vcb7hmip.fsf@toke.dk>

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


> 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.

Note the paper does not work in units of *connections* in section 2, but
rather in terms of *RTT samples*.  So, nearly 5% of the RTT samples add
>= 400msec to the base delay measured for the given remote (in the
"residential" case).

(I am not disagreeing that 400msec of added delay would be noticeable.
I am simply stating what the data actually shows.)

> Now, I may be jumping to conclusions here, but I couldn't find anything
> about how their samples were distributed. 

(I don't follow this comment ... distributed in what fashion?)

> 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.

I agree and this could be done with our data.  (In general, we could go
much deeper into the data on hand ... the paper is an initial foray.)

allman




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

  parent reply	other threads:[~2013-01-08 14:04 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
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 [this message]
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=20130108140445.E493059FB7F@lawyers.icir.org \
    --to=mallman@icir.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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