From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1AD4B3CB35 for ; Fri, 15 Jan 2021 14:28:43 -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=1610738922; bh=phFxpOV/Kd7npP1jsAYDxsy5eVifix9w+vm9otouzPA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=HX2VCYl/K5R9sVsnfXc32zXdIkSqfaZO6anM3EodKvt0M6A3Yd2yGWxcYXy6pPSlA IT1e7CKlQWJcvZrEfh8fkgJBNGexuaK7QI8yrvU/xJgCZTUngx/ZwHqsHlJiUgwBpI umi8t3Trylk95+2+514xH59DnvfS3cvigLJbxiHa2r+KvA7eKd5frs84k6HZ5IODNS tp4Ecsf39e4k7/ienqA2Vw5agZh+UVWrvQQICgyULtmVvSS2LjBfuu/9IherGqQYUi Iaq7eGP587F1hpI0Tjfnq+tj1iVrbFNDhIzLyKceKw6kcrmhuYRZXn+lW2E73kpRfn jdJdihfrKGuwQ== To: Michael Yartys Cc: "make-wifi-fast@lists.bufferbloat.net" In-Reply-To: References: <87a6tarwy3.fsf@toke.dk> <8735z2rpwr.fsf@toke.dk> Date: Fri, 15 Jan 2021 20:28:41 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87zh1aq9sm.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 19:28:43 -0000 Michael Yartys writes: > On Friday, January 15th, 2021 at 19:55, Toke H=C3=B8iland-J=C3=B8rgensen = wrote: > >> Michael Yartys michael.yartys@protonmail.com writes: >>=20 > >> > I assume that I got it right by running: >> >=20 > >> > flent --test-parameter ping_hosts=3D1.1.1.1 -l 300 netperf-eu.bufferbl= oat.net tcp_8down >> >=20 > >> > Either way, I think I'll have to do this test at another time since >> >=20 > >> > someone is streaming TV downstairs (via Ethernet!) and it really >> >=20 > >> > pollutes the results: https://imgur.com/a/F33LjeA >> >=20 > >> > For what it's worth, the ping to 1.1.1.1 looks the same. >>=20 > >> The extra ping flow is not shown by default on the plot with the regular >>=20 > >> ping (for that test), so you'll have to use '-p ping_extra' to see it... > > Thanks for the tip! I use the GUI so I just selected ping_extra under > the plot selector to confirm that they looked similar. Ah, right, I see! OK, in that case it's likely actually something on your networking causing those spikes... Hmm, if this is WiFi I guess it could be periodic interference of some kind? A misbehaving device that's blasting out RF at some interval? -Toke