From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
cake@lists.bufferbloat.net, flent-dev@flent.org
Subject: [Cerowrt-devel] some more reference flent data for cake, fq_codel, pie, codel at 500mbit
Date: Mon, 29 Jun 2015 14:18:04 -0700 [thread overview]
Message-ID: <CAA93jw6KJASMHzx41mYe=j9odmN-TbV1qPBf2pixJp3_wB0WuQ@mail.gmail.com> (raw)
snapon.lab.bufferbloat.net/~d/cake_500.tgz
I was on a 6 hour long conference call. So... why not test a client -
router - server setup while on it?
so this was the nuc - rangeley (with sqm-scripts controlling all) - laptop
No obvious audio glitches, except when I changed qdiscs.
I also used the new qdisc_stats test a little bit along the way.
still somewhat noisy data, of course, but overall trendlines are clear.
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
reply other threads:[~2015-06-29 21:18 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6KJASMHzx41mYe=j9odmN-TbV1qPBf2pixJp3_wB0WuQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=flent-dev@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