From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp96.iad3b.emailsrvr.com (smtp96.iad3b.emailsrvr.com [146.20.161.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 48B753B29D for ; Mon, 10 May 2021 16:10:02 -0400 (EDT) X-Auth-ID: jf@jonathanfoulkes.com Received: by smtp5.relay.iad3b.emailsrvr.com (Authenticated sender: jf-AT-jonathanfoulkes.com) with ESMTPSA id D83C9401C5; Mon, 10 May 2021 16:10:01 -0400 (EDT) From: Jonathan Foulkes Message-Id: <53AB04B4-20D4-48DA-8F62-4746A752ED65@jonathanfoulkes.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_A8CFF4DD-1890-4C68-B7CD-F292FCD3DE63" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Mon, 10 May 2021 16:10:01 -0400 In-Reply-To: Cc: bloat To: "Livingood, Jason" References: X-Mailer: Apple Mail (2.3654.60.0.2.21) X-Classification-ID: ceb47477-eff3-43e0-aaac-376e6db8426d-1-1 Subject: Re: [Bloat] Terminology for Laypeople X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2021 20:10:02 -0000 --Apple-Mail=_A8CFF4DD-1890-4C68-B7CD-F292FCD3DE63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Jason, I=E2=80=99ve found that idle is a good descriptor for unloaded metrics, = and for semi-technical audiences =E2=80=98working=E2=80=99 is a very = good term. But for lay people, the term =E2=80=98loaded=E2=80=99 seems = to work better, especially since we are talking about a metric that = relates to capacity. e.g. When my truck is unloaded, my truck stops quickly, but when loaded, it = takes longer to stop. so now: When my Internet line is unloaded, my latency is low, but when it is = highly loaded (iCloud photo sync), the latency is very high. Cheers, Jonathan Foulkes > On May 4, 2021, at 8:02 PM, Livingood, Jason via Bloat = wrote: >=20 > 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=E2=80=99t really = understand =E2=80=9Ctraditional=E2=80=9D latency vs. latency under load = (LUL). > =20 > As a result, I am planning to experiment in some upcoming briefings = and call traditional latency =E2=80=9Cidle latency=E2=80=9D =E2=80=93 a = measure of latency conducted on an otherwise idle connection. And then = try calling LUL either =E2=80=9Cactive latency=E2=80=9D or perhaps = =E2=80=9Cworking latency=E2=80=9D (suggested by an external colleague = =E2=80=93 can=E2=80=99t take credit for that one) =E2=80=93 to try to = communicate it is latency when the connection is experiencing normal = usage. > =20 > 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? > =20 > Thanks for any input, > Jason > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat = --Apple-Mail=_A8CFF4DD-1890-4C68-B7CD-F292FCD3DE63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Jason,

I=E2=80=99ve = found that idle is a good descriptor for unloaded metrics, and for = semi-technical audiences =E2=80=98working=E2=80=99 is a very good term. = But for lay people, the term =E2=80=98loaded=E2=80=99 seems to work = better, especially since we are talking about a metric that relates to = capacity.

e.g.

When my truck is unloaded, my truck stops quickly, but when = loaded, it takes longer to stop.

so now:

When my Internet line is unloaded, my = latency is low, but when it is highly loaded (iCloud photo sync), the = latency is very high.

Cheers,

Jonathan Foulkes


On May = 4, 2021, at 8: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=E2=80=99t really = understand =E2=80=9Ctraditional=E2=80=9D latency vs. latency under load = (LUL).
 
As a result, I am planning to = experiment in some upcoming briefings and call traditional latency = =E2=80=9Cidle latency=E2=80=9D =E2=80=93 a measure of latency conducted = on an otherwise idle connection. And then try calling LUL either = =E2=80=9Cactive latency=E2=80=9D or perhaps =E2=80=9Cworking latency=E2=80= =9D (suggested by an external colleague =E2=80=93 can=E2=80=99t take = credit for that one) =E2=80=93 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

= --Apple-Mail=_A8CFF4DD-1890-4C68-B7CD-F292FCD3DE63--