From: Dave Taht <dave.taht@gmail.com>
To: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Terminology for Laypeople
Date: Thu, 6 May 2021 07:38:45 -0700 [thread overview]
Message-ID: <CAA93jw60rrxZuOusRFQ2U6t8VEuJUzt=jqR78u1au6U_ORPWTw@mail.gmail.com> (raw)
In-Reply-To: <273096b5-1986-40ad-d169-db30b70a6861@unix-ag.uni-kl.de>
I too like idle and working.
On Wed, May 5, 2021 at 12:42 AM Erik Auerswald
<auerswal@unix-ag.uni-kl.de> wrote:
>
> Hi,
>
> I, too, think that "idle" and "working" seem to be
> useful terms here. An alternative to "idle" might
> be "minimum," since this implies that the latency
> is not always at the minimum.
>
> Thanks,
> Erik
>
> On 05.05.21 02:14, James R Cutler wrote:
> > Jason,
> >
> > I find “idle” and “working” to be understandable both individually and as opposites in almost any field or endeavor. These terms also mesh with typical speed test instructions regarding testing under idle conditions without working internet applications.
> >
> > James
> >
> >> On May 4, 2021, at 7:02 PM, Livingood, Jason via Bloat <bloat@lists.bufferbloat.net> wrote:
> >>
> >> Like many of you I have been immersed in buffer bloat discussions for many years, almost entirely within the technical community. Now that I am starting to explain latency & latency under load to internal non-technical folks, I have noticed some people don’t really understand “traditional” latency vs. latency under load (LUL).
> >>
> >> As a result, I am planning to experiment in some upcoming briefings and call traditional latency “idle latency” – a measure of latency conducted on an otherwise idle connection. And then try calling LUL either “active latency” or perhaps “working latency” (suggested by an external colleague – can’t take credit for that one) – to try to communicate it is latency when the connection is experiencing normal usage.
> >>
> >> Have any of you here faced similar challenges explaining this to non-technical audiences? Have you had any success with alternative terms? What do you think of these?
> >>
> >> Thanks for any input,
> >> Jason
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
next prev parent reply other threads:[~2021-05-06 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 0:02 Livingood, Jason
2021-05-05 0:14 ` James R Cutler
2021-05-05 7:41 ` Erik Auerswald
2021-05-06 14:38 ` Dave Taht [this message]
2021-05-05 1:41 ` Matt Mathis
2021-05-05 15:05 ` Neil Davies
2021-05-06 13:23 ` Jason Iannone
2021-05-06 13:40 ` David Lang
2021-05-06 18:00 ` Dave Taht
2021-05-10 20:10 ` Jonathan Foulkes
2021-05-11 21:26 ` Greg White
2021-05-12 15:50 Ingemar Johansson S
2021-05-12 21:51 ` Dave Collier-Brown
2021-05-16 18:48 ` john
2021-05-16 19:20 ` Jonathan Morton
2021-05-16 20:44 ` Michael Richardson
2021-05-16 21:32 ` Aaron Wood
2021-05-16 21:33 ` Jonathan Morton
2021-05-16 23:02 ` Jonathan Morton
2021-05-17 5:18 ` Simon Barber
2021-05-17 5:24 ` 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/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='CAA93jw60rrxZuOusRFQ2U6t8VEuJUzt=jqR78u1au6U_ORPWTw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=auerswal@unix-ag.uni-kl.de \
--cc=bloat@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