From: Dave Taht <dave.taht@gmail.com>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updated Bufferbloat Test
Date: Wed, 24 Feb 2021 21:35:07 -0800 [thread overview]
Message-ID: <CAA93jw7Ymt2aftZaTCVu8_z+30VFRwQkdW0RAQgABPf1+t4EwA@mail.gmail.com> (raw)
In-Reply-To: <b193ba9c-48b5-93ac-cd12-8a5965e2e6ba@sewingwitch.com>
and with the sqmscripts off?
On Wed, Feb 24, 2021 at 9:29 PM Kenneth Porter <shiva@sewingwitch.com> wrote:
>
> On 2/24/2021 2:15 PM, Kenneth Porter wrote:
> >
> > I'll try to remember to run this from my office tonight when nobody's
> > around. We've got a 50 Mbps fiber connection with AT&T and I'm using
> > fq_codel on a CentOS 7 system for the SQM. That should be interesting.
>
> https://www.waveform.com/tools/bufferbloat?test-id=494dbe95-5302-4e1c-84cd-fbb4c8871ea2
>
> This is after restarting the sqm-scripts. I got initial bad results and
> looked at the debug log and found that the iptables commands were
> failing to get a lock during system boot to set up the mangle table. I
> think it's competing with firewalld and fail2ban and losing. I don't see
> any lock errors from the restart and now the test shows good bloat results.
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-02-25 5:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 18:22 Sina Khanifar
2021-02-24 22:10 ` Dave Taht
2021-02-24 23:39 ` Simon Barber
2021-02-25 5:56 ` Sina Khanifar
2021-02-25 7:15 ` Simon Barber
2021-02-25 7:32 ` Sina Khanifar
2021-02-25 13:38 ` Simon Barber
2021-02-25 13:43 ` Dave Taht
2021-02-25 13:49 ` Mikael Abrahamsson
2021-02-25 13:53 ` Simon Barber
2021-02-25 19:47 ` Sina Khanifar
2021-02-25 19:56 ` Simon Barber
2021-02-25 20:10 ` Sina Khanifar
2021-02-25 20:52 ` Simon Barber
2021-02-25 20:53 ` Simon Barber
2021-02-25 13:46 ` Simon Barber
2021-02-25 7:20 ` Simon Barber
2021-02-25 10:51 ` Sebastian Moeller
2021-02-25 20:01 ` Sina Khanifar
2021-02-25 20:14 ` Sebastian Moeller
2021-02-26 1:06 ` Daniel Lakeland
2021-02-26 8:20 ` Sina Khanifar
2021-02-26 17:25 ` Michael Richardson
2021-02-24 22:15 ` Kenneth Porter
2021-02-25 5:29 ` Kenneth Porter
2021-02-25 5:35 ` Dave Taht [this message]
2021-02-25 6:24 ` Kenneth Porter
2021-02-25 1:16 ` David Collier-Brown
2021-02-25 6:21 ` Sina Khanifar
2021-02-25 4:48 ` Marco Belmonte
[not found] ` <1D68EF40C3A8A269831408C8@172.27.17.193>
2021-02-25 5:58 ` Sina Khanifar
2021-02-25 9:47 ` Mikael Abrahamsson
2021-02-25 10:49 ` Sebastian Moeller
2021-02-25 20:41 ` Sina Khanifar
2021-02-25 20:50 ` Sina Khanifar
2021-02-25 21:15 ` Sebastian Moeller
2021-02-26 8:23 ` Sina Khanifar
2021-02-26 18:41 ` Sina Khanifar
2021-02-26 19:58 ` Sebastian Moeller
2021-02-25 12:27 ` Toke Høiland-Jørgensen
2021-02-25 14:48 ` Toke Høiland-Jørgensen
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7Ymt2aftZaTCVu8_z+30VFRwQkdW0RAQgABPf1+t4EwA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=shiva@sewingwitch.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