Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Dave Täht" <dave@taht.net>
To: Trevor Paskett <snoopytjp@gmail.com>,
	make-wifi-fast@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] AREDN and Make Wifi Fast
Date: Sat, 6 Feb 2016 10:04:17 -0800	[thread overview]
Message-ID: <56B635A1.8080603@taht.net> (raw)
In-Reply-To: <56B63105.5060909@taht.net>

The simplest thing you can do today to improve latency on your ath9k
devices is to disable wmm (802.11e), and to reduce the ath9k driver
queues to smaller sizes. I typically run the yurtlab network with a
qlen_be of 12 (slow links) to 24 rather than the default.

On links with significant speed issues, congestion or interference, I
typically increase the fq_codel target to 20ms.

We have fiddled with using large quantums with per-dst FQ on ptp links
with some success on top of that.

In all cases it helps to have a set of flent runs for each change.
Throughput will drop, fairness and latency will improve. The yurtlab
userbase is generally oblivious to a speed problem, it's having low
latency for gaming, dns, and basic web traffic that works for them.

None of the above are "optimal" fixes in any way, but perhaps you will
get some use from them.

  reply	other threads:[~2016-02-06 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C421D4AF-51DB-4A6B-A240-B6206C71EC9C@gmail.com>
     [not found] ` <CAA93jw5iRyLcDVm6inXUeWkh9seC4fUrEtOfoea1NiSUtsoJJg@mail.gmail.com>
     [not found]   ` <56AA90C9.6050504@taht.net>
     [not found]     ` <C4BFDD36-D50C-4189-AE30-BCA1E4FF2219@gmail.com>
     [not found]       ` <56B0FE22.3050704@taht.net>
     [not found]         ` <73AA134D-76DC-4D37-94F0-CC3C4FEAF5C6@gmail.com>
     [not found]           ` <56B12DE1.8040009@taht.net>
     [not found]             ` <79F77DD2-2BFF-4697-A118-25D17FD06CBB@gmail.com>
     [not found]               ` <56B15105.7040405@taht.net>
     [not found]                 ` <0BAB0F1C-9F93-4579-9426-648CBE1EF5D5@gmail.com>
2016-02-06 17:44                   ` [Cerowrt-devel] " Dave Täht
2016-02-06 18:04                     ` Dave Täht [this message]
2016-02-07 19:18                     ` Stephen Hemminger
2016-02-07 19:36                       ` Dave Taht
2016-03-17 11:00                       ` [Cerowrt-devel] [Make-wifi-fast] " Toke Høiland-Jørgensen
2016-02-27  0:25                     ` David Lang

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=56B635A1.8080603@taht.net \
    --to=dave@taht.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=snoopytjp@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