General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: flent-users <flent-users@flent.org>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] MIT's bufferbloat class
Date: Thu, 20 Sep 2018 15:24:39 -0700	[thread overview]
Message-ID: <CAA93jw4suY2J9cCLDVRhJLVXPSOVyNCCKHkNHkd2urH76K4_Xg@mail.gmail.com> (raw)

It's a bit flawed - not using https, nor a reasonable number of http
assets, averaging the http result rather than plotting it also, with
min/max... nor using flent, nor publishing their source widely so that
I could fiddle with setting up mininet to verify it produces correct
results...

but, it's the first quiz on a class at MIT and it's hard to complain
more than I just did. :) I'm very tempted to try to do this one on my
own, as I strongly suspect the http result to be very misleading.

http://web.mit.edu/6.829/www/currentsemester/psets/pset1/ps1.html

* Start a long lived TCP flow sending data from h1 to h2. Use iperf.
* Start back-to-back ping train from h1 to h2 10 times a second and
record the RTTs.
* Plot the time series of the following:

*The long lived TCP flow's cwnd
* The RTT reported by ping
* Queue size at the bottleneck

Spawn a webserver on h2. Periodically download the index.html web page
using h1 and measure how long it takes to fetch it (on average).
Repeat the above experiment and replot all three graphs after enabling
the PIE AQM algorithm on the switch interface attached to the
bottleneck link. Set the target delay for PIE to 20 ms.
Repeat the above experiment with PIE enabled, but this time, start 10
parallel TCP flows with iperf.


-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

                 reply	other threads:[~2018-09-20 22:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4suY2J9cCLDVRhJLVXPSOVyNCCKHkNHkd2urH76K4_Xg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=flent-users@flent.org \
    /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