General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Collier-Brown <davecb.42@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Terminology for Laypeople
Date: Wed, 12 May 2021 17:51:16 -0400	[thread overview]
Message-ID: <6d93a3cf-7907-c50b-7903-79bd638b5766@indexexchange.com> (raw)
In-Reply-To: <HE1PR0701MB229959935BA40CFB8CBE801CC2529@HE1PR0701MB2299.eurprd07.prod.outlook.com>

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

"lag" is often understood by non-technical folks, as in "the lag between 
the time you step on the gas and the time the car actually speeds up".

Some folks who've been exposed to video enough will know about "lag and 
jitter" (;-))

--dave

On 2021-05-12 11:50 a.m., Ingemar Johansson S via Bloat wrote:
> Hi
>
> Yes. "Idle latency"  and "Working latency" make sense.
>
> Note however that if you think of idle latency as sparse ping, then these sparse ping can give unreasonably high values over cellular access (4G/5G). The reason is here mainly DRX which is a battery saving function in mobile devices. More frequent pings like every 20ms over the course of 100ms or so can give more correct values.
>
> /Ingemar
>
>
>> Message: 1
>> Date: Tue, 11 May 2021 21:26:21 +0000
>> From: Greg White <g.white@CableLabs.com>
>> To: Jonathan Foulkes <jf@jonathanfoulkes.com>, "Livingood, Jason"
>> 	<Jason_Livingood@comcast.com>
>> Cc: bloat <bloat@lists.bufferbloat.net>
>> Subject: Re: [Bloat] Terminology for Laypeople
>> Message-ID: <0A5DF790-7A71-4B84-A20B-559A5E0CE65F@cablelabs.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I recently heard Stuart Cheshire (sort of tongue-in-cheek) refer to “idle
>> latency” as “the latency that users experience when they are not using their
>> internet connection” (or something along those lines).
>>
>> I think terminology that reinforces that the baseline (unloaded) latency is not
>> always what users experience, and that latency under load is not referring to
>> some unusual corner-case situation, is good.  So, I like “idle latency” and
>> “working latency”.
>>
>> -Greg
>>
>>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com |              -- Mark Twain


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

  reply	other threads:[~2021-05-12 21:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 15:50 Ingemar Johansson S
2021-05-12 21:51 ` Dave Collier-Brown [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=6d93a3cf-7907-c50b-7903-79bd638b5766@indexexchange.com \
    --to=davecb.42@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.collier-brown@indexexchange.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