From: Aaron Wood <woody77@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] pie vs. fq - no contest
Date: Tue, 27 May 2014 21:59:22 -0700 [thread overview]
Message-ID: <CALQXh-NAyqLTdbVKHipD5Q+=fxuKp1zF3u5ybNM2VWXKWXzUfQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
http://burntchrome.blogspot.com/2014/05/i-dont-like-this-pie-more-bufferbloat.html
PIE certain is better than nothing. But it's no fq_codel.
All I varied between the two is the queuing discipline, with the PIE target
(both directions) set to 16ms.
not impressed.
But, far better than pie did when I was in Paris, on a 16Mbps down, 1Mbps
up ADSL2+ link:
http://burntchrome.blogspot.com/2014/01/comparing-queue-disciplines-in-cerowrt.html
I think those results were either the default target being wrong, or the
highly asynchronous and highly limited setup being ill-suited to PIE.
Which is concerning, as PIE is going to be deployed in 30/1 cable setups
(like the Numericable.fr setup I had in my first apartment in Paris).
-Aaron
[-- Attachment #2: Type: text/html, Size: 1142 bytes --]
reply other threads:[~2014-05-28 4:59 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='CALQXh-NAyqLTdbVKHipD5Q+=fxuKp1zF3u5ybNM2VWXKWXzUfQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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