Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Pete Heist <pete@eventide.io>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Tue, 24 Apr 2018 15:51:32 +0200	[thread overview]
Message-ID: <87po2o7lwb.fsf@toke.dk> (raw)
In-Reply-To: <EDD97114-2AAA-4F42-A467-B7CC4ACB2BB3@eventide.io>

Pete Heist <pete@eventide.io> writes:

>> On Apr 24, 2018, at 1:54 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> 
>> Pete Heist <pete@eventide.io <mailto:pete@eventide.io>> writes:
>> 
>>> Mean ping time for
>>> cabin 12 is around 200 ms during “active use”, with outliers above 1
>>> second, which is higher than expected. I don’t have data collected on
>>> how many active users that is and what they’re doing, but there could
>>> be 40-50 students around the cabin 12 AP, with however many active "as
>>> is typical for kids”.
>> 
>> Hmm, yeah, 200ms seems quite high. Are there excessive collisions and
>> retransmissions?
>
> Hrm, how would I know that actually? /proc/net/wireless has all zeroes
> in it. I don’t see it anywhere in output from ‘iw’...

Assuming you have debugfs enabled you should be able to get aggregate
statistics from /sys/kernel/debug/ieee80211/phy0/ath9k/xmit - at least
that contains retries, but not backoff data, unfortunately.

There's also the per-station rate data in /sys/kernel/debug/ieee80211/phy0/netdev\:*/stations/*/rc_stats

>> Is the uplink on the same frequency as the clients?
>
> Most definitely, the OM2P-HS is a single channel (2.4 GHz) device,
> with dual antennas. I was hoping the new driver could make the best of
> this situation. :)

Well, in that situation 'the best' may not be terribly good ;)

> Now, my ping test goes from the gateway straight to the repeater, so
> there’s only one WiFi hop in my ping results. I don’t know how pings
> actually look for clients while the AP is under load. I suppose I’ll
> either have to test that manually when I’m on site, or set up a fixed
> wireless SmokePing instance to simulate a client.
>
> I wish I could cable everything, but it isn’t physically practical.
> The next possibility is dual channel APs, or separate backhaul links,
> all costing something...

Yeah, a separate backhaul on a different channel would cut you
contention in half, basically. Right now, each transmission has to
occupy the channel twice...

-Toke

  reply	other threads:[~2018-04-24 13:51 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24  8:33 Pete Heist
2018-04-24 11:54 ` Toke Høiland-Jørgensen
2018-04-24 13:37   ` Pete Heist
2018-04-24 13:51     ` Toke Høiland-Jørgensen [this message]
2018-04-24 14:09       ` Pete Heist
2018-04-24 14:34         ` Toke Høiland-Jørgensen
2018-04-24 19:10           ` Pete Heist
2018-04-24 21:32             ` Toke Høiland-Jørgensen
2018-04-25  6:05               ` Pete Heist
2018-04-25  6:36                 ` Sebastian Moeller
2018-04-25 17:17                   ` Pete Heist
2018-04-26  0:41                 ` David Lang
2018-04-26 19:40                   ` Pete Heist
2018-04-26  0:38               ` David Lang
2018-04-26 21:41                 ` Pete Heist
2018-04-26 21:44                   ` Sebastian Moeller
2018-04-26 21:56                     ` Pete Heist
2018-04-26 22:04                       ` David Lang
2018-04-26 22:47                         ` Pete Heist
2018-04-27 10:15                           ` Toke Høiland-Jørgensen
2018-04-27 10:32                             ` Pete Heist
2018-04-26  0:35       ` David Lang
2018-04-27 11:42 ` Valent Turkovic
2018-04-27 11:50   ` Pete Heist
2018-04-27 11:59     ` Valent Turkovic
2018-04-27 12:17       ` Pete Heist
2018-04-27 11:47 ` Valent Turkovic
2018-04-27 12:00   ` Pete Heist
2018-05-19 16:03 bkil
2018-05-20 18:56 ` Pete Heist
2018-05-31  0:52 ` David Lang
2018-06-08  9:37   ` Pete Heist
2018-06-09 15:32     ` bkil
2018-06-13 13:07       ` Pete Heist
2018-06-13 13:24         ` Toke Høiland-Jørgensen
2018-06-13 16:01           ` Pete Heist
2018-06-30 19:14             ` bkil
2018-07-04 21:47               ` Pete Heist
2018-07-05 13:08                 ` Toke Høiland-Jørgensen
2018-07-05 17:26                   ` Pete Heist
2018-07-05 17:37                     ` Toke Høiland-Jørgensen
2018-07-05 18:02                       ` Pete Heist
2018-07-05 20:17                         ` Jonathan Morton
2018-07-09  2:20                           ` Aaron Wood
2018-07-09  5:17                             ` Jonathan Morton
2018-07-09  6:27                               ` Pete Heist
2018-07-09 12:55                                 ` Sebastian Moeller
2018-07-09 23:21                                   ` Pete Heist
2018-07-09  5:13                 ` David Lang
2018-07-09 23:33               ` Pete Heist
2018-07-10  0:39                 ` Pete Heist
2018-07-10  7:02                   ` bkil
2018-06-13 16:30           ` Sebastian Moeller
2018-06-13 17:50             ` Toke Høiland-Jørgensen
     [not found]       ` <CADuVhRWL2aVjzjfLHg1nPFa8Ae-hWrGrE7Wga4eUKon3oqoTXA@mail.gmail.com>
2018-06-30 19:26         ` bkil
2018-06-30 20:04           ` Jannie Hanekom

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=87po2o7lwb.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=pete@eventide.io \
    /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