Re: [Make-wifi-fast] Weird periodic latency

[Michael Yartys <michael.yartys@protonmail.com>]

I assume that I got it right by running:

flent --test-parameter ping_hosts=1.1.1.1 -l 300 netperf-eu.bufferbloat.net tcp_8down

Either way, I think I'll have to do this test at another time since someone is streaming TV downstairs (via Ethernet!) and it really pollutes the results: https://imgur.com/a/F33LjeA

For what it's worth, the ping to 1.1.1.1 looks the same.

Michael

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, January 15th, 2021 at 17:23, Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Michael Yartys via Make-wifi-fast make-wifi-fast@lists.bufferbloat.net
>
> 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