From: Michael Yartys <michael.yartys@protonmail.com>
To: dave.collier-brown@indexexchange.com, jf@jonathanfoulkes.com,
davecb@spamcop.net
Cc: chromatix99@gmail.com, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Tue, 11 Aug 2020 12:41:50 +0000 [thread overview]
Message-ID: <pF6RlpDgb5O4-Y5HWIR6Ep71gS7mSp_1pdhSnJHVWYPt5oDmqokX2pXUD9wYIFKIjVI-qKEKHsSjctOwMLH3gNKX1BpeamdwjlxgNE_uP9s=@protonmail.com> (raw)
In-Reply-To: <04f2913b-1ee0-c4e7-5c0e-d93a6ac60ca8@indexexchange.com>
[-- Attachment #1: Type: text/plain, Size: 2860 bytes --]
The question I struggle with is how to get ISPs to care and put pressure on CPE manufacturers to fix bufferbloat in their products.
I performed some tests on my Zyxel router, and the WiFi link was terribly bloated when there were a few walls between my laptop and the router. The latency almost reached 10 seconds under load! My ISPs response was that some buffering is normal (some = 10 seconds??) and that artificially saturating the link doesn't represent a normal use case. Keep in mind that this was at the edge of the WiFi coverage with a maximum data rate of 15 Mbps, a speed that's relatively easy to reach. I followed up with an email about how there are solutions to this issue and that they should put pressure on Zyxel to implement them, but alas, there has been no response and it has probably fallen on deaf ears.
Michael
-------- Original Message --------
On 10 Aug 2020, 22:28, Dave Collier-Brown wrote:
> Hi Johnathan, I remember you from before!
>
> On 2020-08-10 1:58 p.m., Jonathan Foulkes wrote:
>
>>> Because of the degree to which we're working from home and videoconferencing, a lot of low-price, medium-performance devices are suddenly too wimpy for their new role.
>>
>> Big time. As noted above, it not just the CPE devices, it’s the congestion on the backhauls that causes issues, and it’s everything from DSL (slammed DSLAMs are endemic) to cable systems with oversubscribed local loops and congested CMTS backhaul. Hell, even fiber to the home ISPs manage to have variable capacity (and bloat) in the evenings.
>
> ...
>
>> Stuff like this article from Jim Gettys on the needs of teachers. BTW- he calls out the IQrouter as his ‘Go to’ recommendation for non-techies. He runs one himself and gave one to his non-techie brother. [Bufferbloat in Action due to Covid-19](https://gettys.wordpress.com/2020/04/22/bufferbloat-in-action-due-to-covid-19/)
>
> Thanks, I hadn't seen that
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.
[-- Attachment #2: Type: text/html, Size: 3915 bytes --]
next prev parent reply other threads:[~2020-08-11 12:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 18:27 David Collier-Brown
2020-08-09 19:18 ` Tom Henderson
2020-08-09 21:35 ` Jonathan Morton
2020-08-10 12:57 ` David Collier-Brown
2020-08-10 14:00 ` Daniel Sterling
2020-08-10 15:08 ` Tom Henderson
2020-08-10 15:34 ` Sebastian Moeller
2020-08-10 15:57 ` Jonathan Morton
2020-08-10 16:04 ` Tom Henderson
2020-08-11 12:43 ` Daniel Sterling
2020-08-11 13:57 ` Kenneth Porter
[not found] ` <D8B6D86243E4539BBA58E32C@172.27.17.193>
2020-08-11 14:09 ` Daniel Sterling
2020-08-11 14:11 ` Daniel Sterling
2020-08-11 16:19 ` Kenneth Porter
2020-08-10 17:58 ` Jonathan Foulkes
2020-08-10 19:13 ` Carlos R. Pasqualini
2020-08-10 20:28 ` Dave Collier-Brown
2020-08-11 12:41 ` Michael Yartys [this message]
2020-08-10 14:16 ` [Bloat] Sidebar to "How about a topical LWN article on demonstrating the real-world goodness of CAKE?" David Collier-Brown
2020-08-11 15:48 ` [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE? Simon Barber
2020-09-05 18:52 ` Dave Taht
2020-09-05 20:35 ` Dave Collier-Brown
2020-09-07 9:23 ` Toke Høiland-Jørgensen
2020-09-07 11:33 ` Dave Collier-Brown
2020-09-07 17:20 ` David Collier-Brown
2020-09-08 15:43 ` Dave Taht
2020-09-08 16:48 ` Matt Mathis
2020-09-08 17:09 ` Jonathan Morton
2020-09-10 15:08 ` Anthony Minessale II
2020-09-10 16:52 ` 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='pF6RlpDgb5O4-Y5HWIR6Ep71gS7mSp_1pdhSnJHVWYPt5oDmqokX2pXUD9wYIFKIjVI-qKEKHsSjctOwMLH3gNKX1BpeamdwjlxgNE_uP9s=@protonmail.com' \
--to=michael.yartys@protonmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.collier-brown@indexexchange.com \
--cc=davecb@spamcop.net \
--cc=jf@jonathanfoulkes.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