From: Michael Welzl <michawe@ifi.uio.no>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Remy: Computer-Generated Congestion Control
Date: Thu, 21 Aug 2014 12:21:49 +0200 [thread overview]
Message-ID: <96292B6B-F49D-4A8A-BD23-DD75399D8DA9@ifi.uio.no> (raw)
In-Reply-To: <CAA93jw5cMxsf68vT2K=44KyksQX2unXmQh=QN1pc6oqfjryHnQ@mail.gmail.com>
Dave,
About this point that I've seen you make repeatedly:
> My biggest problem with all the work so far is that it starts with a
> constant baseline 150ms or 100ms RTT, and then try various algorithms
> over a wide range of bandwidths, and then elides that base RTT in all
> future plots. Unless you read carefully, you don't see that...
>
> The original bufferbloat experiment was at a physical RTT of 10ms,
> with bidirectional traffic flooding the queues in both directions, on
> an asymmetric network. I keep waiting for more experimenters to try
> that as a baseline experiment.
This sounds like a call for reality, when the point is to measure things that matter to the system you're investigating. E.g., if I'm investigating TCP, and I don't specifically work on ACK behavior (ACK congestion control or something like that), I usually don't care much about the backwards traffic or the asymmetry. Yes it does influence the measured RTT a bit, but then you argue for using a smaller base RTT where the impact of this gets smaller too.
What matters to the function of congestion controllers is the BDP, and the buffer size. As for real RTTs, I like pinging wwoz.org because it's a radio station in New Orleans. I do sometimes listen to it, then I get traffic via a TCP connection that has this RTT. Very real. My ping delay is consistently above 110ms.
On a side note, I can't help but mention that the "original bufferbloat experiment" features ping over FQ... measuring ping all by itself, pretty much :-)
Michael
next prev parent reply other threads:[~2014-08-21 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 12:44 Baptiste Jonglez
2014-08-04 14:55 ` Dave Taht
2014-08-21 10:21 ` Michael Welzl [this message]
2014-08-21 17:04 ` Dave Taht
2014-08-21 17:33 ` Jonathan Morton
2014-08-21 19:50 ` Tim Upthegrove
2014-08-21 19:50 ` Alex Burr
2014-08-21 20:57 ` Isaac Konikoff
2014-08-21 19:46 ` Michael Welzl
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=96292B6B-F49D-4A8A-BD23-DD75399D8DA9@ifi.uio.no \
--to=michawe@ifi.uio.no \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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