From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 554933B2A4 for ; Mon, 4 Dec 2017 02:25:00 -0500 (EST) Received: by mail-lf0-x229.google.com with SMTP id r143so17938148lfe.13 for ; Sun, 03 Dec 2017 23:25:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tPNAiPVCHmgvoQODGRzFu8e9RhM7b1iuH6pPJC6jMyU=; b=BkQc5OWzHuRf3mBAuJpfHCLYKxHE09j+AuAK1iah/Qkj99+WQg2451jxuC5CjHloqj mXyHFWmYOwHFGmToeM5/RdwhT/ecpoamDoPGjDaaYPGq3dLri0VljX58Xe75QN31Cayv qVe6WTfoSS2u7OodfkTHsyaHF8MaaHsyFxrsLPj2Z49j0O0VIYgcnbL/qIW6zYIuGZs+ 8484RkWe40MpaiUxWXPTR3QtL4aE2qz0Dr3ZT9W72oLfB8VhJ07g34ujKBlMETfk+sOM yUSf0xED3IVZdy2CSV96SEhyPtR+1AMWlCC6sDugjzhH6R9JSfn/yVdv3js5lFxfs4Dy nPAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tPNAiPVCHmgvoQODGRzFu8e9RhM7b1iuH6pPJC6jMyU=; b=deAj8t/ERAWJYcEuNcRSO37Bj2Bm9uhwKd2wUot+XaFgZW1t7Row8dOsHx+CtdL/mZ DD8qQfoypZUgJOPnc0SgYX2RRzif+J6wx8Kyl8DxVrU7WwX7E6QlDqGjyNAm/Mw0W75i Ujx9fCW3RPXxHZ9YHVjkKHfkQMJr50qGk7nwACI9kqmvgsWXJx7oxwfuSBWrPTaDb/dJ 7gUjptpU16bE9C47iHUVbmciEl/qGQxBH/Xyfut6o/utT5qi1wgNWpicgCLaZ6MYCfYa LchebF4mH1x/FMkd/Goqfg6IZA7cnGaUt45uOPF62QLEzWqaxpTn5c5nQwn9XRyk56Gv QPAw== X-Gm-Message-State: AJaThX7SJcSvofsGVv+ptq1E/pyFqnpy98S2ryzBLx03WTQTj/pWgQS9 iMw+KhscNbfjWEhu+SdJaw2uirTy4eA0wXPsb18= X-Google-Smtp-Source: AGs4zMYG4TjCaoS1iSG9/dEkCc3quDsi4EdxL4MWhDFZJhpaCbr2+5L0qR6RXdbKVs98ywSMEwu0SdffPYHPYzC6KsQ= X-Received: by 10.46.71.143 with SMTP id u137mr8894736lja.79.1512372298910; Sun, 03 Dec 2017 23:24:58 -0800 (PST) MIME-Version: 1.0 References: <20171124092021.DC01D40605C@ip-64-139-1-69.sjc.megapath.net> <4a37c330-cb03-23eb-f705-743c6cb30c15@gmail.com> <877eucr5xg.fsf@nemesis.taht.net> In-Reply-To: <877eucr5xg.fsf@nemesis.taht.net> From: Caleb Cushing Date: Mon, 04 Dec 2017 07:24:47 +0000 Message-ID: To: Dave Taht Cc: Jan Ceuleers , Jonathan Morton , bloat Content-Type: multipart/alternative; boundary="001a11403366a51422055f7e9d29" Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2017 07:25:00 -0000 --001a11403366a51422055f7e9d29 Content-Type: text/plain; charset="UTF-8" So I was going to upload a couple of very large wireshark dumps, but then I looked at something again and realized I was reading one of steam's poorly documented performance metrics wrong. It appears that more often than not now, my problem is actually host or client side on the cpu/encoding, so my network setup is good. I think their may have also been some client side network driver issues. It also seems that even slight alternate network usage can affect the stream (such as leaving a web browser open) all though this seems strange, I can't imagine how that could be impacted one way or another by the router. So thanks for the help. Looking forward to more improvements on your end. On Sun, Nov 26, 2017 at 5:12 PM Dave Taht wrote: > Jan Ceuleers writes: > > > Resending with the from-address with which I'm subscribed to the list > > > > On 26/11/17 18:53, Dave Taht wrote: > >> On Sun, Nov 26, 2017 at 2:05 AM, Jonathan Morton > wrote: > >>> Another explanation for latency spikes on the order of 100ms is that a > >>> periodic (and wholly unnecessary) scan for other APs is run, which > requires > >>> the wifi radio to be temporarily tuned away from the currently > associated > >>> AP's frequency. > >> > >> I'd written that up here: > >> > >> http://blog.cerowrt.org/post/disabling_channel_scans/ > >> > >> Which was improved in some release of network manager > >> > >> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/373680 > > > > Dave, > > > > Thanks, but that's not the same problem I experienced. Yours was > > entirely client-side (i.e. it was behaviour of Network Manager). My > > problem was due to the AP asking the client to periodically perform > > scans (by means of hostapd's obss_interval parameter). > > Got it. Thanks! > > > > > Similar (but not the same) symptoms - different cause. > > > > Jan > > > > > > _______________________________________________ > > Bloat mailing list > > Bloat@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/bloat > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > -- Caleb Cushing http://xenoterracide.com --001a11403366a51422055f7e9d29 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
So I was going to upload a couple of very large wireshark = dumps, but then I looked at something again and realized I was reading one = of steam's poorly documented performance metrics wrong. It appears that= more often than not now, my problem is actually host or client side on the= cpu/encoding, so my network setup is good. I think their may have also bee= n some client side network driver issues. It also seems that even slight al= ternate network usage can affect the stream (such as leaving a web browser = open) all though this seems strange, I can't imagine how that could be = impacted one way or another by the router. So thanks for the help. Looking = forward to more improvements on your end.

On Sun, Nov 26, 2017 at 5:12 PM Dave Taht <dave@taht.net> wrote:
Jan Ceuleers <jan.ceuleers@gmail.com> writes:

> Resending with the from-address with which I'm subscribed to the l= ist
>
> On 26/11/17 18:53, Dave Taht wrote:
>> On Sun, Nov 26, 2017 at 2:05 AM, Jonathan Morton <chromatix99@gmail.com>= wrote:
>>> Another explanation for latency spikes on the order of 100ms i= s that a
>>> periodic (and wholly unnecessary) scan for other APs is run, w= hich requires
>>> the wifi radio to be temporarily tuned away from the currently= associated
>>> AP's frequency.
>>
>> I'd written that up here:
>>
>> http://blog.cerowrt.org/post/disabling= _channel_scans/
>>
>> Which was improved in some release of network manager
>>
>> https://bugs.launchpad= .net/ubuntu/+source/network-manager/+bug/373680
>
> Dave,
>
> Thanks, but that's not the same problem I experienced. Yours was > entirely client-side (i.e. it was behaviour of Network Manager). My > problem was due to the AP asking the client to periodically perform > scans (by means of hostapd's obss_interval parameter).

Got it. Thanks!

>
> Similar (but not the same) symptoms - different cause.
>
> Jan
>
>
> _______________________________________________
> Bloat mailing list
> Bloat= @lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat _______________________________________________
Bloat mailing list
Bloat@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
--
--001a11403366a51422055f7e9d29--