Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Joachim Bodensohn <joachim.bodensohn@adiccon.de>
To: "make-wifi-fast@lists.bufferbloat.net"
	<make-wifi-fast@lists.bufferbloat.net>
Cc: Sebastian Limberg <sebastian.limberg@adiccon.de>
Subject: [Make-wifi-fast] Scaling  airtime weight in dynamic mode
Date: Wed, 25 Aug 2021 11:36:59 +0000	[thread overview]
Message-ID: <FR0P281MB0320EB90C3F94C325977ECD085C69@FR0P281MB0320.DEUP281.PROD.OUTLOOK.COM> (raw)

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

Hello there, 

we did some tests with airtime scheduling in dynamic mode and found, that dynamically calculated weights (256, 512, 768, ..) had no effect upon airtime scheduling and resulting traffic throughput.
The issue seems to be similar as reported by https://lists.bufferbloat.net/pipermail/make-wifi-fast/2020-September/002933.html , because when we made tests with static mode, we had to scale weights to higher values e.g., 45000 and 15000 and set AQL threshold of 5000 and limits per AC 0/5000 to observe the expected outcome.
It seems, that one need some scaling factor in dynamic mode, which scales the results of the dynamic weight calculations to higher values.
Does someone have any idea on how to solve this problem e.g., by scaling the dynamically calculated weights to appropriate values in dynamic mode?

Cheers,
Joachim

Settings:
Measurements have been done with openwrt snapshot releases on "pcengines apu2 with Compex WLE900VX 802.11ac and ath10k" as well as with ubuntu 20.04 with kernel 5.13.0, hostapd 2.9 compiled from scratch and wifi card "QCA986x/988x 802.11ac" with ath10k.
Measurements have been done with four iperf3probes which had been assigned to multi-bss respectively.
Some results are reported in attachments below.
 Attachment 1 shows example of measurements in dynamic mode 
Attachment 2 shows example of measurements in static mode

------------------------------------------------------------------------------------------- 
Joachim Bodensohn, Adiccon GmbH, Telefon: +49 (0) 6151 500 777 - 30, E-Mail: <mailto:joachim.bodensohn@adiccon.de> 



[-- Attachment #2: attachment_1_dynamic_mode.pdf --]
[-- Type: application/pdf, Size: 393021 bytes --]

[-- Attachment #3: attachment_2_static_mode.pdf --]
[-- Type: application/pdf, Size: 446196 bytes --]

             reply	other threads:[~2021-08-25 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 11:36 Joachim Bodensohn [this message]
2021-09-07 19:40 ` Toke Høiland-Jørgensen
     [not found]   ` <FRYP281MB07664DEB0B039187678294A985DB9@FRYP281MB0766.DEUP281.PROD.OUTLOOK.COM>
     [not found]     ` <87v9325bzq.fsf@toke.dk>
     [not found]       ` <FRYP281MB0766177BBFAAB14E1B7AF78385DB9@FRYP281MB0766.DEUP281.PROD.OUTLOOK.COM>
     [not found]         ` <87mtod5yc3.fsf@toke.dk>
     [not found]           ` <FRYP281MB076655B75EDBB6470743EDBA85DC9@FRYP281MB0766.DEUP281.PROD.OUTLOOK.COM>
2021-09-21 11:30             ` Joachim Bodensohn

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=FR0P281MB0320EB90C3F94C325977ECD085C69@FR0P281MB0320.DEUP281.PROD.OUTLOOK.COM \
    --to=joachim.bodensohn@adiccon.de \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=sebastian.limberg@adiccon.de \
    /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