From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Michael Yartys <michael.yartys@protonmail.com>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Weird periodic latency
Date: Fri, 15 Jan 2021 17:23:16 +0100 [thread overview]
Message-ID: <87a6tarwy3.fsf@toke.dk> (raw)
In-Reply-To: <mvG4fyEsjacofj7_jGhA4q9BMA43Mpjdnr9dpBCgouO_-Gb9mD5XLW4aB4uvHlMTsiThtu7SmYj2fEqj_IFSvll59OiT1IBuuYiCJfbLa9k=@protonmail.com>
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
next prev parent reply other threads:[~2021-01-15 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 16:02 Michael Yartys
2021-01-15 16:23 ` Toke Høiland-Jørgensen [this message]
2021-01-15 16:59 ` Michael Yartys
2021-01-15 18:55 ` Toke Høiland-Jørgensen
2021-01-15 19:22 ` Michael Yartys
2021-01-15 19:28 ` Toke Høiland-Jørgensen
[not found] ` <CAA93jw6uLUC9b-vuPrEcL_VqXWPOtqUo=ek2G0x=XmvJ-GfLKw@mail.gmail.com>
2021-01-15 19:10 ` Dave Taht
2021-01-15 19:33 ` Michael Yartys
2021-01-15 21:44 ` Bob McMahon
2021-01-16 14:46 ` Michael Yartys
2021-01-16 17:48 ` Dave Taht
2021-01-16 18:01 ` Michael Yartys
2021-01-16 18:06 ` Dave Taht
2021-01-16 18:14 ` Michael Yartys
2021-01-16 18:20 ` Dave Taht
2021-01-16 21:01 ` Bob McMahon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6tarwy3.fsf@toke.dk \
--to=toke@toke.dk \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox