From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] It's still the starlink latency...
Date: Thu, 29 Sep 2022 11:10:16 +0200 [thread overview]
Message-ID: <CAC=tZ0qubOSaT=pnma0EkxmJN2gNnAer94R2V8VOO=z56k-u7Q@mail.gmail.com> (raw)
I made this video some time ago to illustrate the impact of latency on
what can you achieve during a web browsing session depending on the
latency you have, in this case MEO vs. GEO satellite connection (delay
emulated with netem).
https://www.youtube.com/watch?v=WEl_ud4ME4E
In the end, the latency is accumulated into a delay and it makes you
take more time to achieve the same.
This was done in the frame of the ESA MTAILS project:
https://artes.esa.int/projects/mtails
Off-topic: People poor performance must be first addressed, if not
improved because of a bad attitude, then you lay off, but there is a
whole spectrum of capabilities for people and everybody should be
entitled to contribute as much as they can (and get a reward in
proportion). Otherwise, nobody would employ old people or people with
disabilities, just sharp and smart people in their thirties. Half of
the population starts suffering cognitive decline after the age of
50... Very cruel.
Regards,
David
> Date: Mon, 26 Sep 2022 19:59:04 +0000
> From: Eugene Chang <eugene.chang@alum.mit.edu>
> To: Bruce Perens <bruce@perens.com>
> Cc: Eugene Chang <eugene.chang@alum.mit.edu>, Dave Taht
> <dave.taht@gmail.com>, Dave Taht via Starlink
> <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] It's still the starlink latency...
> Message-ID: <07C46DD5-7359-410E-8820-82B319944618@alum.mit.edu>
> Content-Type: text/plain; charset="utf-8"
>
> The key issue is most people don’t understand why latency matters. They
> don’t see it or feel it’s impact.
>
> First, we have to help people see the symptoms of latency and how it impacts
> something they care about.
> - gamers care but most people may think it is frivolous.
> - musicians care but that is mostly for a hobby.
> - business should care because of productivity but they don’t know how to
> “see” the impact.
>
> Second, there needs to be a “OMG, I have been seeing the action of latency
> all this time and never knew it! I was being shafted.” Once you have this
> awakening, you can get all the press you want for free.
>
> Most of the time when business apps are developed, “we” hide the impact of
> poor performance (aka latency) or they hide from the discussion because the
> developers don’t have a way to fix the latency. Maybe businesses don’t care
> because any employees affected are just considered poor performers. (In bad
> economic times, the poor performers are just laid off.) For employees, if
> they happen to be at a location with bad latency, they don’t know that
> latency is hurting them. Unfair but most people don’t know the issue is
> latency.
>
> Talking and explaining why latency is bad is not as effective as showing why
> latency is bad. Showing has to be with something that has a person impact.
>
> Gene
> -----------------------------------
> Eugene Chang
> eugene.chang@alum.mit.edu
> +1-781-799-0233 (in Honolulu)
>
next reply other threads:[~2022-09-29 9:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:10 David Fernández [this message]
2022-09-29 19:34 ` Eugene Chang
-- strict thread matches above, loose matches on Subject: below --
2022-10-17 13:50 David Fernández
2022-10-17 16:53 ` David Fernández
2022-09-21 18:35 Dave Taht
2022-09-22 11:41 ` Andrew Crane
2022-09-22 12:01 ` Mike Puchol
2022-09-22 13:46 ` warren ponder
2022-09-22 15:07 ` Dave Taht
2022-09-22 15:26 ` Dave Taht
2022-09-26 15:20 ` Livingood, Jason
2022-09-26 15:29 ` Dave Taht
2022-09-26 15:57 ` Sebastian Moeller
2022-09-26 16:21 ` Dave Taht
2022-09-26 16:32 ` Bruce Perens
2022-09-26 19:59 ` Eugene Chang
2022-09-26 20:04 ` Bruce Perens
2022-09-26 20:14 ` Ben Greear
2022-09-26 20:24 ` Bruce Perens
2022-09-26 20:32 ` Dave Taht
2022-09-26 20:36 ` Bruce Perens
2022-09-26 20:47 ` Ben Greear
2022-09-26 20:19 ` Eugene Y Chang
2022-09-26 20:28 ` Dave Taht
2022-09-26 20:32 ` Bruce Perens
2022-09-26 20:35 ` Bruce Perens
2022-09-26 20:48 ` David Lang
2022-09-26 20:54 ` Eugene Y Chang
2022-09-26 21:01 ` Sebastian Moeller
2022-09-26 21:10 ` Eugene Y Chang
2022-09-26 21:20 ` Sebastian Moeller
2022-09-26 21:35 ` Eugene Y Chang
2022-09-26 21:44 ` David Lang
2022-09-26 21:44 ` Bruce Perens
2022-09-27 0:35 ` Dave Taht
2022-09-27 0:55 ` Bruce Perens
2022-09-27 1:12 ` Dave Taht
2022-09-27 4:06 ` Eugene Y Chang
2022-09-27 3:50 ` Eugene Y Chang
2022-09-27 7:09 ` Sebastian Moeller
2022-09-27 22:46 ` Eugene Y Chang
2022-09-28 9:54 ` Sebastian Moeller
2022-09-28 18:49 ` Eugene Y Chang
2022-09-26 21:22 ` David Lang
2022-09-26 21:29 ` Sebastian Moeller
2022-09-27 3:47 ` Eugene Y Chang
2022-09-27 6:36 ` Sebastian Moeller
2022-09-27 13:55 ` Dave Taht
2022-09-28 0:20 ` Eugene Y Chang
2022-09-26 21:02 ` Bruce Perens
2022-09-26 21:14 ` Dave Taht
2022-09-26 21:10 ` Dave Taht
2022-09-26 21:28 ` warren ponder
2022-09-26 21:34 ` Bruce Perens
2022-09-27 16:14 ` Dave Taht
2022-09-26 21:17 ` David Lang
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0qubOSaT=pnma0EkxmJN2gNnAer94R2V8VOO=z56k-u7Q@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=starlink@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