<div dir="ltr">If you want to isolate wifi from the router CPU, connect a device (raspberry pi 4 to the lan switch) and run tests.<br><br>Also, for more detailed testing, sync the clocks to the <a href="https://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html">GPS atomic clock using pulse per second</a> and try out some <a href="https://sourceforge.net/projects/iperf2/">iperf 2.1 </a>new features.<br><br>Bob</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 15, 2021 at 11:33 AM Michael Yartys via Make-wifi-fast <<a href="mailto:make-wifi-fast@lists.bufferbloat.net" target="_blank">make-wifi-fast@lists.bufferbloat.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Friday, January 15th, 2021 at 20:10, Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>> wrote:<br>
<br>
> oops meant to cc the list<br>
><br>
> On Fri, Jan 15, 2021 at 11:09 AM Dave Taht <a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a> wrote:<br>
><br>
> > On Fri, Jan 15, 2021 at 9:00 AM Michael Yartys via Make-wifi-fast<br>
> ><br>
> > <a href="mailto:make-wifi-fast@lists.bufferbloat.net" target="_blank">make-wifi-fast@lists.bufferbloat.net</a> wrote:<br>
> ><br>
> > > I assume that I got it right by running:<br>
> > ><br>
> > > flent --test-parameter ping_hosts=1.1.1.1 -l 300 <a href="http://netperf-eu.bufferbloat.net" rel="noreferrer" target="_blank">netperf-eu.bufferbloat.net</a> tcp_8down<br>
> > ><br>
> > > 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: <a href="https://imgur.com/a/F33LjeA" rel="noreferrer" target="_blank">https://imgur.com/a/F33LjeA</a><br>
> ><br>
> > I wouldn't say that pollutes the results, I'd say those are the<br>
> ><br>
> > typical and terrible results most users get when trying to do more<br>
> ><br>
> > than one thing at once on wifi or over the internet. Also it helps to<br>
> ><br>
> > have sqm on your isp updownlink, especially with netflix as it is<br>
> ><br>
> > bursty as heck<br>
> ><br>
> > I do not know if aql is enabled on that chipset. To my eye, it isn't,<br>
> ><br>
> > but the induced latency isn't quite high enough to represent what I<br>
> ><br>
> > viewed as the baseline problems.<br>
<br>
Yup, AQL is enabled on this chipset, and I also have SQM piece_of_cake enabled to 50/50 mbps. I ran another test and made sure that there was no significant activity on the wireless network before I started it. Here are the results: <a href="https://imgur.com/a/7MzMVVJ" rel="noreferrer" target="_blank">https://imgur.com/a/7MzMVVJ</a><br>
<br>
And the ping to 1.1.1.1 has the same shape: <a href="https://imgur.com/a/drcTGfv" rel="noreferrer" target="_blank">https://imgur.com/a/drcTGfv</a><br>
<br>
Looks quite weird to me with all the oscillating latency spikes.<br>
> ><br>
> > <a href="https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002" rel="noreferrer" target="_blank">https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002</a><br>
> ><br>
> > Do a packet capture at the AP and look for multciast bursts especially<br>
<br>
I think I'll have to find a moment where I have the network to myself again to be able to properly test things and figure out what might be causing this stuff. I'll probably do a packet capture at some point.<br>
<br>
> ><br>
> > And I keep trying to set aside time to go deep on AQL again, as the<br>
> ><br>
> > 7800 is a pretty popular box...<br>
> ><br>
> > > For what it's worth, the ping to 1.1.1.1 looks the same.<br>
> > ><br>
> > > Michael<br>
> > ><br>
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
> > ><br>
> > > On Friday, January 15th, 2021 at 17:23, Toke Høiland-Jørgensen <a href="mailto:toke@toke.dk" target="_blank">toke@toke.dk</a> wrote:<br>
> > ><br>
> > > > Michael Yartys via Make-wifi-fast <a href="mailto:make-wifi-fast@lists.bufferbloat.net" target="_blank">make-wifi-fast@lists.bufferbloat.net</a><br>
> > > ><br>
> > > > writes:<br>
> > > ><br>
> > > > > Hi<br>
> > > > ><br>
> > > > > I decided to run a couple of flent 8-stream TCP downloads from<br>
> > > > ><br>
> > > > > <a href="http://netperf-eu.bufferbloat.net" rel="noreferrer" target="_blank">netperf-eu.bufferbloat.net</a> to my Fedora 33 laptop, and I noticed some<br>
> > > > ><br>
> > > > > weird periodic latency in the resulting graphs. My router is the<br>
> > > > ><br>
> > > > > NETGEAR R7800 running OpenWrt with an ath10k radio. Here's a graph<br>
> > > > ><br>
> > > > > that's representative of the results that I got:<br>
> > > > ><br>
> > > > > <a href="https://imgur.com/a/BOKNzht" rel="noreferrer" target="_blank">https://imgur.com/a/BOKNzht</a><br>
> > > > ><br>
> > > > > This looks similar to the latency spikes you would get from channel<br>
> > > > ><br>
> > > > > scans, but I have specified the BSSID in the Gnome network settings,<br>
> > > > ><br>
> > > > > which means that background scanning should be disabled. In addition,<br>
> > > > ><br>
> > > > > the test ran for 30 minutes, and channel scans are much more frequent<br>
> > > > ><br>
> > > > > than the latency spikes seen in the graph above. Here's what channel<br>
> > > > ><br>
> > > > > scans look like in a 15 minute long test: <a href="https://imgur.com/a/YJepfcp" rel="noreferrer" target="_blank">https://imgur.com/a/YJepfcp</a><br>
> > > > ><br>
> > > > > Does anyone here know what could be causing this behaviour?<br>
> > > ><br>
> > > > Hmm, your email reminds me that the server you are testing against was<br>
> > > ><br>
> > > > having some issue before the holidays. So it may just be that it's<br>
> > > ><br>
> > > > crapping out and it has nothing to do with your connection.<br>
> > > ><br>
> > > > You could try adding a secondary ping flow (--test-parameter<br>
> > > ><br>
> > > > ping_hosts=one.one.one.one should do it) and see if that secondary flow<br>
> > > ><br>
> > > > also shows the same spikes. If it does, it's likely your connection, if<br>
> > > ><br>
> > > > not it's likely the server...<br>
> > > ><br>
> > > > -Toke<br>
> > ><br>
> > > Make-wifi-fast mailing list<br>
> > ><br>
> > > <a href="mailto:Make-wifi-fast@lists.bufferbloat.net" target="_blank">Make-wifi-fast@lists.bufferbloat.net</a><br>
> > ><br>
> > > <a href="https://lists.bufferbloat.net/listinfo/make-wifi-fast" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/make-wifi-fast</a><br>
> ><br>
> > --<br>
> ><br>
> > "For a successful technology, reality must take precedence over public<br>
> ><br>
> > relations, for Mother Nature cannot be fooled" - Richard Feynman<br>
> ><br>
> > <a href="mailto:dave@taht.net" target="_blank">dave@taht.net</a> <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729<br>
><br>
> --<br>
><br>
> "For a successful technology, reality must take precedence over public<br>
><br>
> relations, for Mother Nature cannot be fooled" - Richard Feynman<br>
><br>
> <a href="mailto:dave@taht.net" target="_blank">dave@taht.net</a> <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729<br>
_______________________________________________<br>
Make-wifi-fast mailing list<br>
<a href="mailto:Make-wifi-fast@lists.bufferbloat.net" target="_blank">Make-wifi-fast@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/make-wifi-fast" rel="noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/make-wifi-fast</a></blockquote></div>
<br>
<span style="background-color:rgb(255,255,255)"><font size="2">This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.</font></span>