From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Rigorous Coffee Shop Bloat Testing
Date: Tue, 3 Sep 2019 19:13:38 -0700 [thread overview]
Message-ID: <30c6d641-b0e5-7a8f-103f-4d6f2ff0286b@sewingwitch.com> (raw)
In-Reply-To: <20190903174046.68f24735@hermes.lan>
On 9/3/2019 5:40 PM, Stephen Hemminger wrote:
> There was a recent Wall Street Journal article that faster Internet doesn't mean anything.
> https://www.wsj.com/graphics/faster-internet-not-worth-it/
>
> I just thought "faster Internet just exposes your existing Bufferbloat"
I hit a paywall trying to read that so I looked up the article title and
found some interesting commentary:
https://tech.slashdot.org/story/19/08/20/1450204/the-truth-about-faster-internet-its-not-worth-it
https://stopthecap.com/2019/08/20/wall-street-journal-says-faster-internet-not-worth-it-but-they-ignore-bottlenecks-and-data-caps/
Most people are streamers and won't fill a fat pipe. The big winners of
fast Internet are people who want to download a huge game and play it
quickly. But those are rare. (I'm a gamer but I'm patient and can wait a
day to play so I'm happy to save money on a cheaper package that can be
used for something else.)
As you say, when people report slow Internet, it's probably bloat, not
the speed of the package. But faster packages make money for the ISPs.
next prev parent reply other threads:[~2019-09-04 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 15:57 Rich Brown
2019-09-03 17:29 ` Dave Taht
2019-09-04 0:03 ` Kenneth Porter
2019-09-04 0:40 ` Stephen Hemminger
2019-09-04 2:13 ` Kenneth Porter [this message]
2019-09-04 3:17 ` Dave Taht
2019-09-04 3:24 ` Jonathan Morton
2019-09-04 5:49 ` Stephen Hemminger
2019-10-04 19:05 ` Dave Taht
2019-10-04 19:22 ` Dave Collier-Brown
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=30c6d641-b0e5-7a8f-103f-4d6f2ff0286b@sewingwitch.com \
--to=shiva@sewingwitch.com \
--cc=bloat@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