General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi
Date: Sun, 19 Nov 2017 14:13:32 -0800	[thread overview]
Message-ID: <CAA93jw7YqeAtOjXbif4EM6qP4nF3y6eP0THvKmLb4Pc9oQN+Ww@mail.gmail.com> (raw)
In-Reply-To: <CAAHKNRF6xJf_drbujqV0B8nco-1Cmh49eRYn==CtcmQ4P9Fn6g@mail.gmail.com>

On Sun, Nov 19, 2017 at 2:03 PM, Caleb Cushing <xenoterracide@gmail.com> wrote:
>>
>> 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.
>
>
> I could try running wireshark on both, it's a ton of packets, and I'll be
> honest, I don't know that *I* would know what to do with them.
>
>>
>> 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...
>
>
> steam homestreaming has an in game performance monitor, it shows you your
> ping, estimated bandwidth, and how fast it's currently streaming. So when
> the game stutters I also notice a recorded ping/latency increase. Sadly
> though, it doesn't include highly detailed logs to my knowledge.
>
>> Yeah, those are link-layer retransmissions. The ath9k driver sometimes
>> retries individual packets up to 30 times, which is obviously way too
>> much...
>
>
> that's fun...

Ideally we should retry at most, twice, at the lowest rate, and a bit
more as we go up.

> --
> Caleb Cushing
>
> http://xenoterracide.com
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2017-11-19 22:13 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
2017-11-19 22:03       ` Caleb Cushing
2017-11-19 22:13         ` Dave Taht [this message]
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=CAA93jw7YqeAtOjXbif4EM6qP4nF3y6eP0THvKmLb4Pc9oQN+Ww@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    --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