From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 89EFF3B29E for ; Sun, 19 Nov 2017 16:28:19 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1511126896; bh=k6ajLXlsnu/+rxtZrGlG3LUKLdD+zSEXOUG97Aw+lhs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=YSXmlMAXFg7EoMhjd+SDz0o5YWkZwwOx8pA34sI1EkRMJAQT9rqjfDHP1Gpr7mGYu Ri8XGYOcDxoCp2UlIUd4hjWGbQJioqAjUz78JyiTaLXHAOx42Nb9ObY5RtLm1c08h6 i81wcj3aQ33gy4A/1+yrhT4kCVEMX5pmkzHhMPaiPVF8DWG9yyyzvQeNVi+tXucqW1 A9gpcEqFrcQMAylJ8c+5JeK95jyjhomR3BeYMMy6tAIHP0CnvZ/bHtpUk3wzzS8E2X j34oymJYqbzIRQLzO3sA+XeBL0hM8cAqIFfEafJgC8i/aJXRReFcFc45I21g46zGuT nxURr7EGY8qCQ== To: Caleb Cushing Cc: bloat@lists.bufferbloat.net In-Reply-To: References: <8760a6b5ce.fsf@toke.dk> Date: Sun, 19 Nov 2017 22:27:02 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87tvxq9cyh.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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 21:28:19 -0000 Caleb Cushing 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