From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tsiox almost gets fixing bufferbloat right on reddit
Date: Sat, 7 Mar 2015 10:09:02 -0500 [thread overview]
Message-ID: <75DD1E1D-9E6E-41FB-9C6D-0F1DD36F5068@gmail.com> (raw)
In-Reply-To: <CAA93jw7cZjzgJgTdWC55M1tP1MfpWr5YG127kubHETweyJFpcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
It seems that tsiox (on Reddit) is advocating that people invert the usual shotgun approach of guessing which QoS policies to implement, and instead use the following steps if "the network is slow":
- The first line of defense is minimizing queues in the bottleneck routers. Using fq_codel, pie, or other traffic shaping policy really makes a huge difference without spending time on configuration.
- After the traffic shaping is in place, measure the traffic responsiveness. If you can tell that the traffic shapers aren't quite doing the trick, then implement QoS, but only for the critical traffic that needs prioritization.
- And of course, you may actually need more bandwidth. (The example in the Reddit thread of 100 video feeds at 1Mbps - you're going to *require* a 100 Mbps feed. No amount of queue management, prioritization, etc. will help.)
Questions:
- Is this a good policy, properly stated?
- Is it something we should espouse on the Bloat/CeroWrt sites?
Rich
On Mar 7, 2015, at 8:26 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I am nervous about applying sch_fq in this scenario rather than
> fq_codel but it is late - and honestly I have never tried what he
> suggests, can't remember my handle on reddit, and the guy otherwise
> gets it, in multiple postings on reddit elsewhere.
>
> http://www.reddit.com/r/networking/comments/2xm5gs/qos_policy/
>
> Can I ask that someone else monitor reddit, and chat with this guy, so
> I don't have to?
>
> --
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-03-07 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 13:26 Dave Taht
2015-03-07 15:09 ` Rich Brown [this message]
2015-03-07 15:43 ` 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=75DD1E1D-9E6E-41FB-9C6D-0F1DD36F5068@gmail.com \
--to=richb.hanover@gmail.com \
--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