General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi
Date: Sun, 19 Nov 2017 22:27:02 +0100	[thread overview]
Message-ID: <87tvxq9cyh.fsf@toke.dk> (raw)
In-Reply-To: <CAAHKNREOp4s-Po=Q3GyQyq6LZi-Gcxap6qCLbDdaXbABOEoT=w@mail.gmail.com>

Caleb Cushing <xenoterracide@gmail.com> writes:

>>
>>
>> So this is two computers talking to each other over WiFi? What
>> chipsets/drivers are they using for WiFi? It may very well be that what
>> you're seeing is hickups in the WiFi connection at the computer, not at
>> the router. In which case there's nothing you can do on the router to
>> fix it.
>>
>
> sure possible, can't say it's not, I did manage to find a channel that
> only I'm on in the 5 ghz range and all machines are within 2 meters of
> the AP. But of course it's wifi so, no real guarantees.
>
> Both computers are running windows 10. Server is running a qualcomm
> device says it's using the killer wireless n/a/c version 4.0.2.26
> (fishy, I know killer wireless is sort of it's own qos, I think I've
> effectively disabled it though). Client is running an Intel Dual Band
> wireless AC 8260, driver 19.71.1.1.

Right, no idea how Windows drivers behave. But odds are that the
bottleneck is at the client, since that often has worse antennas than
the AP. If you're in a position to take packet captures at both clients
and AP you may be able to figure it out; may require tightly
synchronised clocks to do properly, though.

How do you see the latency spikes? An end-to-end ping? You could try
pinging the AP from both clients and see which one sees the latency
spike...

>> Another possibility is that it's an occasional signal drop that causes
>> excessive retries (either at the router or the AP). We have not gotten
>> around to limiting the retries in the drivers yet, so that can cause
>> quite a bit of very intermittent head of line blocking as well.
>>
> could also be, do those retries happen when it's udp? 'cause I think
> steam homestreaming is basically all udp, maybe the packets are just
> getting dropped?

Yeah, those are link-layer retransmissions. The ath9k driver sometimes
retries individual packets up to 30 times, which is obviously way too
much...

-Toke

  reply	other threads:[~2017-11-19 21:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 22:14 Caleb Cushing
2017-11-19 16:28 ` Toke Høiland-Jørgensen
2017-11-19 21:18   ` Caleb Cushing
2017-11-19 21:27     ` Toke Høiland-Jørgensen [this message]
2017-11-19 22:03       ` Caleb Cushing
2017-11-19 22:13         ` Dave Taht
2017-11-21 19:08 Hal Murray
2017-11-22 10:31 ` Neil Davies
2017-11-23 17:48   ` Caleb Cushing
2017-11-24  9:20   ` Hal Murray
2017-11-24  9:34     ` Neil Davies
2017-11-26  7:25       ` Caleb Cushing
2017-11-26  7:29         ` Caleb Cushing
2017-11-26  7:55           ` Jan Ceuleers
2017-11-26 10:05             ` Jonathan Morton
2017-11-26 10:53               ` Jan Ceuleers
2017-11-26 10:55                 ` Jonathan Morton
2017-11-26 11:54                 ` Steinar H. Gunderson
2017-11-26 13:03                   ` Jan Ceuleers
2017-11-26 13:05                     ` Jan Ceuleers
2017-11-26 13:13                       ` Steinar H. Gunderson
2017-11-26 17:53               ` Dave Taht
2017-11-26 18:43                 ` Jan Ceuleers
2017-11-26 23:11                   ` Dave Taht
2017-12-04  7:24                     ` Caleb Cushing

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=87tvxq9cyh.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=xenoterracide@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