From: Dave Taht <dave.taht@gmail.com>
To: netalyzr <netalyzr@icsi.berkeley.edu>,
"aqm@ietf.org" <aqm@ietf.org>,
mnot@mnot.net, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] fixing bufferbloat on bigpond cable...
Date: Wed, 11 Mar 2015 19:11:33 -0700 [thread overview]
Message-ID: <CAA93jw59q6sWCfEjD2giY2GbMMTuSBDrAXYQLAir_fnnSoE7Ww@mail.gmail.com> (raw)
I was very pleased to see this tweet go by today:
https://twitter.com/mnot/status/575581792650018816
where Mark Nottingham fixed his bufferbloat on bigpond cable
using a very simple htb + fq_codel script. (I note ubnt edgerouters
also have a nice gui for that, as does openwrt)
But: he does point out a flaw in netanalyzr's current tests[1], in that
it does not correctly detect the presence of aqm or FQing on the link,
(in part due to not running long enough, and also in not using
multiple distinct flows) and like the "ping loss considered harmful"
thread last week on the aqm and bloat lists, matching user
expectations and perceptions would be good with any public
tests that exist.
There is some stuff in the aqm evaluation guide's "burst tolerance"
tests that sort of applies, but... ideas?
[1] I am not aware of any other tests for FQ than mine, which are still
kind of hacky. What I have is in my isochronous repo on github.
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
next reply other threads:[~2015-03-12 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 2:11 Dave Taht [this message]
2015-03-12 2:14 ` Mark Nottingham
2015-03-12 2:23 ` Dave Taht
2015-03-12 2:31 ` Dave Taht
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=CAA93jw59q6sWCfEjD2giY2GbMMTuSBDrAXYQLAir_fnnSoE7Ww@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=mnot@mnot.net \
--cc=netalyzr@icsi.berkeley.edu \
/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