From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] It’s the Latency, FCC
Date: Sat, 16 Mar 2024 18:21:48 +0100 [thread overview]
Message-ID: <d04bf060-54e2-4828-854e-29c7f3e3de98@gmail.com> (raw)
In-Reply-To: <fa80c0da-80a3-448f-9691-57fea644f8c0@gmail.com>
I retract the message, sorry, it is true that some teleoperation and
visioconf also use 4K. So the latency is important there too.
A visioconf with 8K and 3D 16K might need latency reqs too.
Le 16/03/2024 à 18:18, Alexandre Petrescu via Starlink a écrit :
>
> Le 15/03/2024 à 21:31, Colin_Higbie via Starlink a écrit :
>> Spencer, great point. We certainly see that with RAM, CPU, and
>> graphics power that the software just grows to fill up the space. I
>> do think that there are still enough users with bandwidth constraints
>> (millions of users limited to DSL and 7Mbps DL speeds) that it
>> provides some pressure against streaming and other services requiring
>> huge swaths of data for basic functions, but, to your point, if there
>> were a mandate that everyone would have 100Mbps connection, I agree
>> that would then quickly become saturated so everyone would need more.
>>
>> Fortunately, the video compression codecs have improved dramatically
>> over the past couple of decades from MPEG-1 to MPEG-2 to H.264 to VP9
>> and H.265. There's still room for further improvements, but I think
>> we're probably getting to a point of diminishing returns on further
>> compression improvements. Even with further improvements, I don't
>> think we'll see bandwidth needs drop so much as improved quality at
>> the same bandwidth, but this does offset the natural
>> bloat-to-fill-available-capacity movement we see.
>
> I think the 4K-latency discussion is a bit difficult, regardless of
> how great the codecs are.
>
> For one, 4K can be considered outdated for those who look forward to
> 8K and why not 16K; so we should forget 4K. 8K is delivered from
> space already by a japanese provider, but not on IP. So, if we
> discuss TV resolutions we should look at these (8K, 16K, and why not
> 3D 16K for ever more strength testing).
>
> Second, 4K etc. are for TV. In TV the latency is rarely if ever an
> issue. There are some rare cases where latency is very important in
> TV (I could think of betting in sports, time synch of clocks) but they
> dont look at such low latency as in our typical visioconference or
> remote surgery or group music playing use-cases on Internet starlink.
>
> So, I dont know how much 4K, 8K, 16K might be imposing any new latency
> requirement on starlink.
>
> Alex
>
>>
>>
>> -----Original Message-----
>> From: Spencer Sevilla
>> Sent: Friday, March 15, 2024 3:54 PM
>> To: Colin_Higbie
>> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
>> Subject: Re: [Starlink] It’s the Latency, FCC
>>
>> Your comment about 4k HDR TVs got me thinking about the bandwidth
>> “arms race” between infrastructure and its clients. It’s a particular
>> pet peeve of mine that as any resource (bandwidth in this case, but
>> the same can be said for memory) becomes more plentiful, software
>> engineers respond by wasting it until it’s scarce enough to require
>> optimization again. Feels like an awkward kind of malthusian
>> inflation that ends up forcing us to buy newer/faster/better devices
>> to perform the same basic functions, which haven’t changed almost at
>> all.
>>
>> I completely agree that no one “needs” 4K UHDR, but when we say this
>> I think we generally mean as opposed to a slightly lower codec, like
>> regular HDR or 1080p. In practice, I’d be willing to bet that there’s
>> at least one poorly programmed TV out there that doesn’t downgrade
>> well or at all, so the tradeoff becomes "4K UHDR or endless
>> stuttering/buffering.” Under this (totally unnecessarily forced upon
>> us!) paradigm, 4K UHDR feels a lot more necessary, or we’ve otherwise
>> arms raced ourselves into a TV that can’t really stream anything. A
>> technical downgrade from literally the 1960s.
>>
>> See also: The endless march of “smart appliances” and TVs/gaming
>> systems that require endless humongous software updates. My stove
>> requires natural gas and 120VAC, and I like it that way. Other stoves
>> require… how many Mbps to function regularly? Other food for thought,
>> I wonder how increasing minimum broadband speed requirements across
>> the country will encourage or discourage this behavior among network
>> engineers. I sincerely don’t look forward to a future in which we all
>> require 10Gbps to the house but can’t do much with it cause it’s all
>> taken up by lightbulb software updates every evening /rant.
>>
>>> On Mar 15, 2024, at 11:41, Colin_Higbie via Starlink
>>> <starlink@lists.bufferbloat.net> wrote:
>>>
>>>> I have now been trying to break the common conflation that download
>>>> "speed"
>>>> means anything at all for day to day, minute to minute, second to
>>>> second, use, once you crack 10mbit, now, for over 14 years. Am I
>>>> succeeding? I lost the 25/10 battle, and keep pointing at really
>>>> terrible latency under load and wifi weirdnesses for many existing
>>>> 100/20 services today.
>>> While I completely agree that latency has bigger impact on how
>>> responsive the Internet feels to use, I do think that 10Mbit is too
>>> low for some standard applications regardless of latency: with the
>>> more recent availability of 4K and higher streaming, that does
>>> require a higher minimum bandwidth to work at all. One could argue
>>> that no one NEEDS 4K streaming, but many families would view this as
>>> an important part of what they do with their Internet (Starlink
>>> makes this reliably possible at our farmhouse). 4K HDR-supporting
>>> TV's are among the most popular TVs being purchased in the U.S.
>>> today. Netflix, Amazon, Max, Disney and other streaming services
>>> provide a substantial portion of 4K HDR content.
>>>
>>> So, I agree that 25/10 is sufficient, for up to 4k HDR streaming.
>>> 100/20 would provide plenty of bandwidth for multiple concurrent 4K
>>> users or a 1-2 8K streams.
>>>
>>> For me, not claiming any special expertise on market needs, just my
>>> own personal assessment on what typical families will need and care
>>> about:
>>>
>>> Latency: below 50ms under load always feels good except for some
>>> intensive gaming (I don't see any benefit to getting loaded latency
>>> further below ~20ms for typical applications, with an exception for
>>> cloud-based gaming that benefits with lower latency all the way down
>>> to about 5ms for young, really fast players, the rest of us won't be
>>> able to tell the difference)
>>>
>>> Download Bandwidth: 10Mbps good enough if not doing UHD video
>>> streaming
>>>
>>> Download Bandwidth: 25 - 100Mbps if doing UHD video streaming,
>>> depending on # of streams or if wanting to be ready for 8k
>>>
>>> Upload Bandwidth: 10Mbps good enough for quality video conferencing,
>>> higher only needed for multiple concurrent outbound streams
>>>
>>> So, for example (and ignoring upload for this), I would rather have
>>> latency at 50ms (under load) and DL bandwidth of 25Mbps than latency
>>> of 1ms with a max bandwidth of 10Mbps, because the super-low latency
>>> doesn't solve the problem with insufficient bandwidth to watch 4K
>>> HDR content. But, I'd also rather have latency of 20ms with 100Mbps
>>> DL, then latency that exceeds 100ms under load with 1Gbps DL
>>> bandwidth. I think the important thing is to reach "good enough" on
>>> both, not just excel at one while falling short of "good enough" on
>>> the other.
>>>
>>> Note that Starlink handles all of this well, including kids watching
>>> YouTube while my wife and I watch 4K UHD Netflix, except the upload
>>> speed occasionally tops at under 3Mbps for me, causing quality
>>> degradation for outbound video calls (or used to, it seems to have
>>> gotten better in recent months – no problems since sometime in 2023).
>>>
>>> Cheers,
>>> Colin
>>>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2024-03-16 17:21 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` Colin Higbie
2024-03-15 18:41 ` Colin_Higbie
2024-03-15 19:53 ` Spencer Sevilla
2024-03-15 20:31 ` Colin_Higbie
2024-03-16 17:18 ` Alexandre Petrescu
2024-03-16 17:21 ` Alexandre Petrescu [this message]
2024-03-16 17:36 ` Sebastian Moeller
2024-03-16 22:51 ` David Lang
2024-03-15 23:07 ` David Lang
2024-03-16 18:45 ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 19:09 ` Sebastian Moeller
2024-03-16 19:26 ` Colin_Higbie
2024-03-16 19:45 ` Sebastian Moeller
2024-03-16 23:05 ` David Lang
2024-03-17 15:47 ` [Starlink] It’s " Colin_Higbie
2024-03-17 16:17 ` [Starlink] Sidebar to It’s the Latency, FCC: Measure it? Dave Collier-Brown
2024-03-16 18:51 ` [Starlink] It?s the Latency, FCC Gert Doering
2024-03-16 23:08 ` David Lang
2024-04-30 0:39 ` [Starlink] It’s " David Lang
2024-04-30 1:30 ` [Starlink] Itʼs " Colin_Higbie
2024-04-30 2:16 ` David Lang
2024-05-06 15:42 [Starlink] It’s " David Fernández
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 13:21 David Fernández
2024-05-03 9:09 [Starlink] It's " David Fernández
[not found] <mailman.2877.1714641707.1074.starlink@lists.bufferbloat.net>
2024-05-02 14:47 ` [Starlink] It’s " Colin_Higbie
2024-05-02 19:50 ` Frantisek Borsik
2024-05-06 11:19 ` Alexandre Petrescu
2024-05-06 13:43 ` Nathan Owens
2024-05-06 15:22 ` Colin_Higbie
2024-05-14 19:23 ` Colin_Higbie
2024-05-15 6:52 ` Sebastian Moeller
2024-05-15 14:55 ` Colin_Higbie
2024-05-03 1:48 ` Ulrich Speidel
2024-05-03 7:22 ` Jeremy Austin
2024-05-03 9:02 ` Alexandre Petrescu
2024-05-03 8:29 ` Alexandre Petrescu
2024-05-03 8:34 ` Alexandre Petrescu
2024-05-01 16:35 [Starlink] It's " David Fernández
2024-05-01 8:41 David Fernández
[not found] <mailman.2785.1714507537.1074.starlink@lists.bufferbloat.net>
2024-04-30 20:48 ` [Starlink] It’s " Colin Higbie
2024-04-30 20:49 ` Colin_Higbie
2024-05-01 0:51 ` David Lang
[not found] <mailman.2779.1714503924.1074.starlink@lists.bufferbloat.net>
2024-04-30 19:31 ` Colin_Higbie
2024-04-30 19:51 ` Eugene Y Chang
2024-04-30 21:07 ` Dave Taht
2024-04-30 21:22 ` Frantisek Borsik
2024-04-30 22:02 ` Dave Taht
2024-04-30 22:03 ` Dave Taht
2024-04-30 22:05 ` [Starlink] Fwd: " Rich Brown
2024-04-30 22:10 ` Dave Taht
2024-04-30 22:42 ` [Starlink] " Rich Brown
2024-04-30 23:06 ` Dave Taht
2024-04-30 22:31 ` Eugene Y Chang
2024-04-30 21:22 ` Eugene Y Chang
2024-04-30 21:35 ` Frantisek Borsik
2024-04-30 21:53 ` Eugene Y Chang
2024-05-01 0:54 ` David Lang
2024-05-01 7:27 ` Frantisek Borsik
2024-05-01 19:26 ` Eugene Y Chang
2024-05-14 16:05 ` Dave Taht
[not found] <mailman.2775.1714488970.1074.starlink@lists.bufferbloat.net>
2024-04-30 19:12 ` Colin_Higbie
2024-04-30 19:31 ` Eugene Y Chang
2024-05-01 0:33 ` David Lang
2024-05-01 0:31 ` David Lang
2024-05-01 0:40 ` [Starlink] It?s " David Lang
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s " Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-02 9:09 ` Alexandre Petrescu
2024-05-02 9:28 ` Ulrich Speidel
2024-04-30 20:05 ` Sebastian Moeller
2024-05-02 9:21 ` Alexandre Petrescu
[not found] <mailman.2769.1714483871.1074.starlink@lists.bufferbloat.net>
2024-04-30 14:00 ` Colin_Higbie
2024-04-30 14:25 ` Alexandre Petrescu
2024-04-30 14:32 ` Sebastian Moeller
2024-04-30 14:40 ` Alexandre Petrescu
2024-04-30 14:45 ` Sebastian Moeller
2024-04-30 14:56 ` Alexandre Petrescu
2024-04-30 15:04 ` David Lang
2024-04-30 15:01 ` David Lang
2024-04-30 9:54 David Fernández
[not found] <mailman.2495.1710610618.1074.starlink@lists.bufferbloat.net>
2024-03-16 19:10 ` Colin_Higbie
2024-03-16 19:32 ` Sebastian Moeller
2024-03-17 17:00 ` Alexandre Petrescu
2024-03-17 19:26 ` Frantisek Borsik
2024-03-15 3:53 Larry Press
2024-03-15 5:33 ` Dave Taht
2024-03-15 21:14 ` 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/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=d04bf060-54e2-4828-854e-29c7f3e3de98@gmail.com \
--to=alexandre.petrescu@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