From: Michael Yartys <michael.yartys@protonmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "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 19:22:11 +0000 [thread overview]
Message-ID: <VqEulU4cJgEwvvV05TKS5obsuZd_qGlK0tRIXsjBhnx7i6iZYZD4Ps8UxOpN83JYioAWh8KXFX7PacgxfVUC3m_eySjXtfRKlK9njMX26tI=@protonmail.com> (raw)
In-Reply-To: <8735z2rpwr.fsf@toke.dk>
On Friday, January 15th, 2021 at 19:55, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Michael Yartys michael.yartys@protonmail.com writes:
>
> > 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.
>
> The extra ping flow is not shown by default on the plot with the regular
>
> 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.
>
> -Toke
next prev parent reply other threads:[~2021-01-15 19:22 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
2021-01-15 16:59 ` Michael Yartys
2021-01-15 18:55 ` Toke Høiland-Jørgensen
2021-01-15 19:22 ` Michael Yartys [this message]
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='VqEulU4cJgEwvvV05TKS5obsuZd_qGlK0tRIXsjBhnx7i6iZYZD4Ps8UxOpN83JYioAWh8KXFX7PacgxfVUC3m_eySjXtfRKlK9njMX26tI=@protonmail.com' \
--to=michael.yartys@protonmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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