General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Martin Geddes <mail@martingeddes.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat in high resolution + non-stationarity
Date: Mon, 16 Oct 2017 13:26:56 -0700	[thread overview]
Message-ID: <87y3oaq1nz.fsf@nemesis.taht.net> (raw)
In-Reply-To: <CAAAY2ag-tjrOFHzfoDPVhqB3r=6Eo8ZwJDA3mwsHUwKX8R1Bhw@mail.gmail.com> (Martin Geddes's message of "Wed, 11 Oct 2017 14:00:04 +0100")


Sorry for the late reply.

Martin Geddes <mail@martingeddes.com> writes:

> Folks,
>
> I have uploaded a presentation of high-fidelity network performance measures
> which includes an example of bufferbloat in high resolution, as possibly you
> have never seen it before.

Well, flent can generate a similar level of detail under a generated
load. Some of kathie's work can now do it against tcp on pcaps.

Was yours against general traffic?

>
> See slide 18 of this deck:
> https://www.slideshare.net/mgeddes/stationarity-is-the-new-speed. The classic
> "bloat" is a sudden formation of the queue, and a very slow (and steady)
> draining. Bufferbloat is just one form of statistical variability
> ("non-stationarity") in packet networks.

Good set of slides. Analysis is picking up...

Where you and I always tend to fall off a cliff is on your conclusions
as to what to do about it, e.g. slide 19. I'd rather love it if you
repeated your tests and graphs against pie, and fq_codel, and/or cake.

For that matter BBR might be interesting against your tool.

And then say what you'd do differently. In some way I can repeat.

> For a world record winner, see this one where packets take over a minute (Huawei
> WiFi hotspot roaming in Ireland with UK SIM)! Or for a pretty picture of buffers
> draining, try this one.

Well, at the moment gogo-in-flight holds the interplanetary record
(680sec as I recall), but yea, 60+ seconds is up there. Contact
Guinness!

>
> Happy to answer any questions.
>
> Martin Geddes
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2017-10-16 20:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 13:00 Martin Geddes
2017-10-16 20:26 ` Dave Taht [this message]
2017-11-25 20:23 Martin Geddes
2017-11-26 12:20 ` Toke Høiland-Jørgensen
2017-11-27 23:16   ` Martin Geddes
2017-11-27 23:55     ` Dave Taht
2017-11-28  2:07       ` Aaron Wood
2017-11-28 11:03     ` Toke Høiland-Jørgensen
     [not found]       ` <CAJq5cE3rWztd0f307bb-3H_tp5pvaHX_7Vp++PiwcU1X5eB_BQ@mail.gmail.com>
     [not found]         ` <CAJq5cE2jqAzAWoQB+3b9smq4ZvmBLoC5xE3oFYcQ+OVB+JCYgg@mail.gmail.com>
2017-11-28 16:16           ` Jonathan Morton
2017-11-30 12:31             ` Neil Davies
2017-11-30 16:51               ` Jonathan Morton
2017-11-30 19:59                 ` Mikael Abrahamsson
2017-11-30 20:09                   ` Jonathan Morton
2017-12-01  9:06                     ` Michael Welzl
     [not found]                       ` <CAJq5cE2_aiiJGdPOHQnEbfOqPVKLRP05AW1X6XLwSNaU233h=w@mail.gmail.com>
2017-12-01 13:48                         ` Jonathan Morton
2017-11-28 23:57       ` Martin Geddes
2017-11-29 11:57         ` Toke Høiland-Jørgensen

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=87y3oaq1nz.fsf@nemesis.taht.net \
    --to=dave@taht.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=mail@martingeddes.com \
    /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