From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: davecb@spamcop.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] an observation from the field
Date: Wed, 29 Aug 2018 10:20:09 +0200 [thread overview]
Message-ID: <CAM9iV=KzS-3XOMUif6N7-V8KxXyaJ8cKXk8fD=ngSApe24To+Q@mail.gmail.com> (raw)
In-Reply-To: <D92B8A42-FCD8-4962-B4FF-4378D2D24BB9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]
Hi Jonathan,
On Wed, Aug 29, 2018 at 2:16 AM Jonathan Morton <chromatix99@gmail.com>
wrote:
> > On 29 Aug, 2018, at 2:53 am, David Collier-Brown <davec-b@rogers.com>
> wrote:
> >
> > Humans experience delays directly, and so perceive systems with high
> latency as "slow". The proverbial "man on the Clapham omnibus" therefor
> responds to high-latency systems with disgust.
> >
> > A trained scientist, however, runs the risk of choosing something that
> requires complicated measurement schemes, and might well choose to optimize
> for throughput, as that sounds like a desirable measure, one matching their
> intuitions of what "fast" means.
>
> The correct approach, for scientists, is to observe that for many
> applications, response time (a form of latency) is the *only* relevant
> metric. In some cases, higher bandwidth correlates with reduced response
> time, such as for software updates. In other cases, bandwidth is
> essentially irrelevant, except as it pertains to serialisation delay of
> single packets.
>
Yes, exactly, thank you for bringing some actual scientific reasoning into
the discussion. It would actually be nice to have a tool for measuring
"response time" for different applications
>
> Conversely, there are some applications for which sufficient bandwidth is
> not a matter of response time, but a threshold prerequisite for correct
> operation. We can refer to these as isochronous applications, or choose
> another term if you prefer. Video streaming is an example of this; given
> an a-priori chosen video codec setting, if the data it produces cannot be
> transferred as fast as it is produced, the receiver will not be able to
> play it back in synchrony.
>
> YouTube can reliably stream Full-HD (1080p60) video down a 10Mbps
> debloated pipe. The broadband standard in the US claims that 25Mbps is
> necessary for this precise application.
No, it doesn't. It claims the opposite, i.e. that 10Mbps is sufficient for
streaming one HD video but with 25Mbps you can stream two HD videos or one
4K video, see Table 1 in the FCC report:
https://docs.fcc.gov/public/attachments/FCC-15-10A1.pdf
/Jonas
> Draw your own conclusions.
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 3417 bytes --]
next prev parent reply other threads:[~2018-08-29 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 17:07 Dave Taht
2018-08-28 18:22 ` Jonathan Foulkes
2018-08-28 23:53 ` David Collier-Brown
2018-08-29 0:16 ` Jonathan Morton
2018-08-29 8:20 ` Jonas Mårtensson [this message]
2018-08-29 15:37 ` Dave Taht
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='CAM9iV=KzS-3XOMUif6N7-V8KxXyaJ8cKXk8fD=ngSApe24To+Q@mail.gmail.com' \
--to=martensson.jonas@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=davecb@spamcop.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