From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [LibreQoS] summarizing the bitag latency report?
Date: Fri, 11 Nov 2022 16:48:56 -0700 [thread overview]
Message-ID: <CAA_JP8WLNr8FDnH=1Pf6v_X5OeX1spd0axcjAkFLT2o30GkHcQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4MXxRnzchsETc7mgT0xdAkxs4vG0MoNu=GfQ4u8ALLqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
I used to run a pizza franchise so I go back to that a lot haha. Latency
(when talking to an end user) is the time between when you order your pizza
and it shows up at your door. The streets to your house are the internet.
If the streets are clear and the weather's good and the pizza store is
running smoothly, it'll arrive when expected. If the roads are terrible,
or traffic is heavy it'll be late. If there roads are packed or
congested, or if they are in bad shape, or too small, or the pizza place is
just really far away, then the pizza is going to take more time to get
there. The pizza delivery guy takes more time to get to their first
delivery, and then more time to get to you, then more time to get back.
I also lean on this to describe internet 'speed' as 'capacity' and say it's
a misnomer. It doesn't matter how much pizza you order, the 'speed' is how
quickly they process your order and get it to you which is heavily
dependent on the latency details. If you order more pizza, it takes a
bigger bag and then eventually a bigger vehicle but since the pizza guy
doesn't have a semi, he has to take multiple trips if you order too much.
Speed is the capacity of his car. Mbps is pizza pies per car.
Am I getting into the weeds to much here lol
On Fri, Nov 11, 2022 at 4:16 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> If you were to try to summarize this *in a paragraph*, what would you say?
>
> https://www.bitag.org/documents/BITAG_latency_explained.pdf
>
> (yes, I helped write this, but squeezing it down to less than 3 pages
> is beyond my capabilities, much less a paragraph, and by the time we
> hit the recommendations section, things had got too political to make
> sane recommendations)
>
> Also QoS, vs QoE. Try to imagine explaining the need to a CFO, or
> congresscritter. Feel free to take more than a paragraph.
>
>
> --
> 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: 3079 bytes --]
next prev parent reply other threads:[~2022-11-11 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:16 Dave Taht
2022-11-11 23:48 ` dan [this message]
2022-11-12 8:39 ` [LibreQoS] [Bloat] " Sebastian Moeller
2022-11-12 13:14 ` Sebastian Moeller
2022-11-12 14:38 ` Herbert Wolverson
2022-11-12 15:00 ` Dave Taht
2022-11-12 15:03 ` Herbert Wolverson
2022-11-14 17:05 ` Jonathan Morton
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='CAA_JP8WLNr8FDnH=1Pf6v_X5OeX1spd0axcjAkFLT2o30GkHcQ@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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