From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 AFC453B29E for ; Sun, 19 Nov 2017 17:04:03 -0500 (EST) Received: by mail-lf0-x22d.google.com with SMTP id y2so7074822lfj.4 for ; Sun, 19 Nov 2017 14:04:03 -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=9l/YjGbAwrBdNm4em/khYyuaOQqpoid/BrPHyETt5iQ=; b=BJz79Amil9c4sFhIl99qUU71hNUVNDOVc5wiadGFgeeX2YBKcez3BnQhrpfJYNVhhI qfbRet0K4R8dO2yQOx/q4JyjZj1Isq8JojxwW80KMY8PJdfU9PtIbPq2ZvAAhDBl7pZ2 8i+A9Mth1HX01k9JRTz/Vvco6de2eKRJymbVtTmBrBU90ev+kLY1qXAL1seYrPbJWX+G /WYrKBJBLVZWnxI3Vwg649p1hmRu+yR93wkbdDAOeDZqvbdfHGkEps0aV0vd8qZNTMCm Kiv10GPhKc3CPRMwPAyV69P8RamJejkG2imrwGKibjuJ1cSh1VDRkvLs4kNxWHQyRDA3 /0Zw== 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=9l/YjGbAwrBdNm4em/khYyuaOQqpoid/BrPHyETt5iQ=; b=YGVV9KFpI3dcn1i/bQ2SZ2q2EvhuZoo4hc0YU9z0CmQFKw2KOE4ASQV+Uf55OYIRqY Hy8Mb72gfrEj+TVL/fkOehOVWdn3uiuyVaI9/ujafyf0Dwrd2Lknh9/KUy6ExytZgSDs lvkSAeTsUeTz4NAx7yKvtKLZy1LF/7wAOd+iyFJq/4Yxtur/20KTFmDmpSTcSV4TcEVT 2ZyQVtyOEYPhxumUDrnEsdoUVi/bCS03EcGmgm6nngsfQgrMDRNPUHRj7LaUeATd8O7J QGNU7a54MD2RfgVz//4FSDj0d+KStiVnq3CYxFxblaR3YMeQkZAs8Gdy+2Tb7zHnCvLn bsJw== X-Gm-Message-State: AJaThX6e1eYg/0e5PXJ8OVNIDfI/tbCiDE3HzpDSPvbH0GfEmL1Ud/tk FuXIzqQ01QOyfCOvYQe0ftMECWbiL8446fCNIX4= X-Google-Smtp-Source: AGs4zMZNwatit20UZm3Oebg8CJhX0JP/Why+NTO0D3h1S5D4ZZ1JRaCK1/fqmX8XYtbq4WjXV+CxvXUxAvhs1+Xt7Vc= X-Received: by 10.46.91.129 with SMTP id m1mr3159323lje.185.1511129042427; Sun, 19 Nov 2017 14:04:02 -0800 (PST) MIME-Version: 1.0 References: <8760a6b5ce.fsf@toke.dk> <87tvxq9cyh.fsf@toke.dk> In-Reply-To: <87tvxq9cyh.fsf@toke.dk> From: Caleb Cushing Date: Sun, 19 Nov 2017 22:03:51 +0000 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="94eb2c1aad08c8a543055e5d2510" 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: Sun, 19 Nov 2017 22:04:03 -0000 --94eb2c1aad08c8a543055e5d2510 Content-Type: text/plain; charset="UTF-8" > > > 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... -- Caleb Cushing http://xenoterracide.com --94eb2c1aad08c8a543055e5d2510 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
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 th= em.=C2=A0


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 not= ice 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...=C2=A0
--
Caleb Cushing --94eb2c1aad08c8a543055e5d2510--