From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9325E3CB35 for ; Fri, 15 Jan 2021 11:23:22 -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=1610727798; bh=NON9Nbtx94FIqOwdnK/Cp2Q33k0iRNo3TP6hmmudMLk=; h=From:To:Subject:In-Reply-To:References:Date:From; b=pZU/Sy1WMInwJ6yOOuMPgx+PBowqlocaOuaW3yGScfGq6OLVWobH6hHS+GT1IsIu7 iSI4P3rBLWqu+k+x6oIFno6haFU82/FXkAM4nefn4g8ZAt91zIUavesD9VGckn10Xu P3fbc1/TU4Ch9vKgfEgsDU9Mr/sMogP9pVSE4F0taq+PKxbETFB24UgC/nRT7xikq1 6/vpdes3AbqvO83Yo8NsdZsBvBTrwmpIoExM2BEGVKWYvQBBVWgkEIpZxDNSUCZiW2 apmZE9tK6a5DDcVnMI9U+CGYP71ZpCvUu/9i64XCMP1JGT/Pc1SCs2kF/TlIpDm2mg cNb+h4qHQOKyw== To: Michael Yartys , "make-wifi-fast@lists.bufferbloat.net" In-Reply-To: References: Date: Fri, 15 Jan 2021 17:23:16 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87a6tarwy3.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] Weird periodic latency X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2021 16:23:22 -0000 Michael Yartys via Make-wifi-fast writes: > Hi > > I decided to run a couple of flent 8-stream TCP downloads from > netperf-eu.bufferbloat.net to my Fedora 33 laptop, and I noticed some > weird periodic latency in the resulting graphs. My router is the > NETGEAR R7800 running OpenWrt with an ath10k radio. Here's a graph > that's representative of the results that I got: > https://imgur.com/a/BOKNzht > > This looks similar to the latency spikes you would get from channel > scans, but I have specified the BSSID in the Gnome network settings, > which means that background scanning should be disabled. In addition, > the test ran for 30 minutes, and channel scans are much more frequent > than the latency spikes seen in the graph above. Here's what channel > scans look like in a 15 minute long test: https://imgur.com/a/YJepfcp > > Does anyone here know what could be causing this behaviour? Hmm, your email reminds me that the server you are testing against was having some issue before the holidays. So it may just be that it's crapping out and it has nothing to do with your connection. You could try adding a secondary ping flow (--test-parameter ping_hosts=one.one.one.one should do it) and see if that secondary flow also shows the same spikes. If it does, it's likely your connection, if not it's likely the server... -Toke