Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Herbert Wolverson <herberticus@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] ookla speedtest results?
Date: Mon, 24 Oct 2022 09:01:55 -0500	[thread overview]
Message-ID: <CA+erpM4+ck16xa4eSm08QALtXiKqkftfuAdF3rK38mZcprLjvw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7YYhB9kJ=sVmRtMBM3EUkXimvaP_mDBTfZbbuH9Azzcw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

Are you looking for a shaped result? That'll show "whatever bandwidth
is left on the sector" without Libre, and around the customer's paid-for
target with Libre (hopefully!).

One thing Preseem does well is that their onboarding process includes
"leave it in monitoring-only mode" for a week, gathering data before you
pull the switch (although most ISPs I've talked to just pull the switch...)
It's quite enlightening to see a before/after, even with only FQ_CODEL
as the shaper.

We could probably do something similar with a "monitor only" mode that
doesn't enable any queues (is there a TC equivalent to "dummy" on
FreeBSD?).

On Mon, Oct 24, 2022 at 8:52 AM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> I am curious if anyone here has speedtest results with libreqos on and
> off, and can send a screen shot?
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>

[-- Attachment #2: Type: text/html, Size: 2024 bytes --]

  reply	other threads:[~2022-10-24 14:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 13:51 Dave Taht
2022-10-24 14:01 ` Herbert Wolverson [this message]
2022-10-24 15:02   ` Robert Chacón
2022-10-24 15:09     ` Dave Taht
2022-10-24 15:20       ` dan
2022-10-24 15:27         ` Dave Taht
2022-10-24 15:31           ` dan
2022-10-24 16:30             ` Herbert Wolverson
2022-10-24 16:48               ` dan
2022-10-24 17:14                 ` Dave Taht
2022-10-24 17:30                   ` dan
2022-10-24 17:39                     ` Dave Taht
2022-10-24 17:34                   ` Robert Chacón
2022-10-24 17:41                     ` Herbert Wolverson
2022-10-24 17:42                     ` Dave Taht
2022-10-24 17:46                       ` dan
2022-10-24 17:57                         ` Dave Taht
2022-10-24 18:03                           ` dan
2022-10-24 18:06                             ` Herbert Wolverson
2022-10-24 18:22                               ` Dave Taht
2022-10-24 18:27                                 ` Dave Taht
2022-10-24 20:16                                   ` Robert Chacón
2022-10-24 20:31                                     ` Dave Taht
2022-10-24 20:49                                       ` Mark Steckel
2022-10-24 18:14                             ` Dave Taht

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/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+erpM4+ck16xa4eSm08QALtXiKqkftfuAdF3rK38mZcprLjvw@mail.gmail.com \
    --to=herberticus@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /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