From: Sebastian Moeller <moeller0@gmx.de>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Global CDN Services Market About $5B in 2023, Expected To Grow 3%
Date: Fri, 12 Jul 2024 12:48:44 +0200 [thread overview]
Message-ID: <2DF0AD48-9E93-48A9-8813-73ABDC164A89@gmx.de> (raw)
In-Reply-To: <CAJUtOOi6riQecLShaaDpss93k+oAwpu+izA=ySOyGQ3pzRCD-A@mail.gmail.com>
Hi Frank,
> On 12. Jul 2024, at 12:31, Frantisek Borsik via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> <1720708860160.jpeg>
>
> Blog post: https://www.streamingmediablog.com/2024/07/cdn-market-size.html
>
> Podcast: https://www.danrayburnpodcast.com/1893312/15332762-special-cdn-podcast-the-latest-data-on-pricing-market-size-tech-trends-diy-revenue-and-performance
>
> There was a term "Low Latency" discussed and I'm kind of confused:
>
> <Screenshot 2024-07-12 at 12.29.59 PM.png>
>
>
> All the best,
>
> FrankFrantisek (Frank) Borsik
> https://www.linkedin.com/in/frantisekborsik
I guess the issue is that bad latency typically is causing a quantitative degradation, not a big qualitative step that is immediately noticeable. People can learn/train themselves to operate in high latency/high intertia environments (steering a big loaded container ship). Sure that might not be pleasant, but I bet quite a lot of people affected by this can not put their finger on it and explicitly state what is wrong... a content provider muight take the wrong message from that inability of end users to localize the root cause?
> Signal, Telegram, WhatsApp: +421919416714
> iMessage, mobile: +420775230885
> Skype: casioa5302ca
> frantisek.borsik@gmail.com
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2024-07-12 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 10:31 Frantisek Borsik
2024-07-12 10:48 ` Sebastian Moeller [this message]
2024-07-12 13:21 ` Livingood, Jason
2024-07-12 23:41 ` Michael Richardson
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=2DF0AD48-9E93-48A9-8813-73ABDC164A89@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.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