Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Adrian Popescu <adriannnpopescu@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] bloated ath10k
Date: Sun, 10 Feb 2019 16:37:16 +0200	[thread overview]
Message-ID: <CAF3M4P0HoYw4M_UJjDtmwjOieTEBWWgh=nxTO3s0Wvbug9BAGQ@mail.gmail.com> (raw)
In-Reply-To: <3CB198EB-2844-42DB-9E5A-26708BFD7304@gmail.com>

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

Running a wire isn't an option for devices which don't have ethernet ports.

I'll try to run some tests with flent to figure out what's happening. A
constant latency of 20-30 ms isn't a big deal. The spikes which cause
stuttering during a voice or video call are the real problem. The
stuttering may not have been caused by these spikes.

It seems that these routers don't have enough power to do traffic shaping,
NAT and to forward hundreds of mbps of data. It might be interesting to
compare the idle latency with the latency under load. I've also considered
running some tests with mac80211_hwsim. mac80211_hwsim may not provide the
option to simulate a deep buffer like the ath10k one and may not be as
relevant.



On Sun, Feb 10, 2019 at 2:38 PM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 10 Feb, 2019, at 2:24 pm, Adrian Popescu <adriannnpopescu@gmail.com>
> wrote:
> >
> > My attempts to use SQM and codel to reduce wifi bloat didn't seem to get
> me very far. 802.11ac seems more reliable and it seems to be more bloated.
> ath9k can go as low as 3-5 milliseconds. ath10k is usually in the 20-50
> milliseconds range (or more, based on the number of stations). I usually
> test with a single client as I don't expect latency to improve with more
> clients.
>
> Some things are unavoidable when you move to a shared, half-duplex, noisy
> medium like wifi versus a switched, full-duplex, error-free medium like
> Ethernet.
>
> If you're getting 20-50ms under load, then I think things are working
> quite well with wifi.  We can wish for better, but not long ago you could
> be looking at multiple seconds in bad cases.  At the levels you're now
> seeing, ordinary interactive protocols like DNS and HTTP will work reliably
> and quickly, and even VoIP should be able to cope; you'll likely only
> really notice a problem with online games.
>
> Ath9k has some advantages over ath10k in this area.  Its MAC is managed at
> a lower level by the driver, so we have much more control over it when
> trying to debloat.  I think we still have more control over ath10k than
> most of the alternatives.
>
> If low latency is mission critical, though - just run a wire.
>
>  - Jonathan Morton
>
>

[-- Attachment #2: Type: text/html, Size: 2746 bytes --]

  reply	other threads:[~2019-02-10 14:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10 12:24 Adrian Popescu
2019-02-10 12:38 ` Jonathan Morton
2019-02-10 14:37   ` Adrian Popescu [this message]
2019-02-10 19:00   ` David P. Reed
2019-02-11  2:18     ` Bob McMahon
2019-02-11  3:03       ` Bob McMahon
2019-02-11 14:47       ` David P. Reed
2019-02-11 18:07         ` Bob McMahon

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='CAF3M4P0HoYw4M_UJjDtmwjOieTEBWWgh=nxTO3s0Wvbug9BAGQ@mail.gmail.com' \
    --to=adriannnpopescu@gmail.com \
    --cc=chromatix99@gmail.com \
    --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