Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Dave Täht" <dave@taht.net>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] BARD?
Date: Sun, 25 Dec 2016 14:40:00 -0500	[thread overview]
Message-ID: <c8c99f30-1d45-39dd-b50e-3fcbe68ba36c@taht.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]


One of next year's probable projects is to incorporate the features in
minstrel-blues into mainline minstrel. Given just how hard it is to see
wins in this area I'd propose renaming the thing to something else so a
given box can be easily A/B switched and compared between regular
minstrel and whatever emerges from that effort.

BARD - Basic Adaptive Rate Decimator?

There are quite a few things in rate control worth looking at.

Also, the ath9k retries figure is still at a really high value. I long
ago cut it to < 8 (I think I used 6), but never pushed up the patch
(hard to measure) and is probably responsible for a few of the whiskers
of excess jitter here. A fixed number of retries is basically the wrong
thing, anyway... should end up time/airtime based vs the workload.

Still, testing a ubntlite today at 25 feet and 3 walls, it's nice to see
the ath9k outperform the ath10k in terms of bandwidth, be comparable in
terms of latency, and superior in terms of jitter.

OSX client ->

ath9k: HT20, channel 11
ath10k: VHT80, channel 153 (I think)


[-- Attachment #2: ath10ath9compared.png --]
[-- Type: image/png, Size: 49194 bytes --]

[-- Attachment #3: ath9_ubntlite.png --]
[-- Type: image/png, Size: 191172 bytes --]

[-- Attachment #4: ath10.png --]
[-- Type: image/png, Size: 152685 bytes --]

                 reply	other threads:[~2016-12-25 19:40 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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8c99f30-1d45-39dd-b50e-3fcbe68ba36c@taht.net \
    --to=dave@taht.net \
    --cc=make-wifi-fast@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