From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Long-RTT broken again
Date: Wed, 11 Nov 2015 10:23:17 +0000 [thread overview]
Message-ID: <56431715.7030902@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw5BnwL-QNo6ZNmpyoh6v2oosSdNJ5Boe7Rgb2qG7+8nyw@mail.gmail.com>
On 08/11/2015 16:29, Dave Taht wrote:
> Applause all around!
>
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> https://www.gofundme.com/savewifi
Indeed! I don't know when this bug first surfaced, or if it's
effectively always been there, but I can definitely report an
improvement in marks vs drops vs packet loss under load since the fix
went in...and that's even on a standard 100ms rtt link. For those
vaguely interested, I monitor my home broadband link with
'Thinkbroadband's Broadband quality monitor. It sends a ping packet
every second and measures the reply (or not) simple but useful monitor.
Here's a link to my active monitor
http://www.thinkbroadband.com/ping/share/c716f7a50c999e580588859eccd2cf3a.html
- vertical red spikes are probably me fiddling with firmware ;-)
prev parent reply other threads:[~2015-11-11 10:23 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 16:53 Toke Høiland-Jørgensen
2015-11-02 18:29 ` Sebastian Moeller
2015-11-03 1:39 ` Jonathan Morton
2015-11-03 8:20 ` Sebastian Moeller
2015-11-03 8:25 ` Jonathan Morton
2015-11-03 8:34 ` Sebastian Moeller
2015-11-03 10:29 ` Kevin Darbyshire-Bryant
2015-11-03 11:08 ` Sebastian Moeller
2015-11-03 11:45 ` Toke Høiland-Jørgensen
2015-11-03 11:57 ` Toke Høiland-Jørgensen
2015-11-03 12:41 ` Sebastian Moeller
2015-11-03 11:50 ` Toke Høiland-Jørgensen
2015-11-03 16:43 ` Jonathan Morton
2015-11-03 17:05 ` Toke Høiland-Jørgensen
2015-11-03 17:11 ` Sebastian Moeller
2015-11-03 17:25 ` Toke Høiland-Jørgensen
2015-11-03 17:31 ` Jonathan Morton
2015-11-03 17:33 ` Toke Høiland-Jørgensen
2015-11-03 17:46 ` Sebastian Moeller
2015-11-03 17:49 ` Toke Høiland-Jørgensen
2015-11-03 17:52 ` Sebastian Moeller
2015-11-03 17:54 ` Toke Høiland-Jørgensen
2015-11-03 17:57 ` Sebastian Moeller
2015-11-03 17:59 ` Toke Høiland-Jørgensen
2015-11-03 18:06 ` Sebastian Moeller
2015-11-03 19:17 ` Jonathan Morton
2015-11-03 19:24 ` Sebastian Moeller
2015-11-05 14:36 ` Toke Høiland-Jørgensen
2015-11-05 19:30 ` Jonathan Morton
2015-11-06 11:00 ` Toke Høiland-Jørgensen
2015-11-06 14:15 ` Toke Høiland-Jørgensen
2015-11-06 15:09 ` Toke Høiland-Jørgensen
2015-11-07 5:02 ` Jonathan Morton
2015-11-07 5:16 ` Dave Taht
2015-11-07 6:49 ` Jonathan Morton
2015-11-07 8:48 ` Toke Høiland-Jørgensen
2015-11-07 10:51 ` Jonathan Morton
2015-11-07 13:06 ` Jonathan Morton
2015-11-07 13:42 ` Toke Høiland-Jørgensen
2015-11-07 16:34 ` Toke Høiland-Jørgensen
2015-11-07 13:44 ` Toke Høiland-Jørgensen
2015-11-07 15:08 ` Sebastian Moeller
2015-11-07 16:24 ` Toke Høiland-Jørgensen
2015-11-07 18:25 ` Sebastian Moeller
2015-11-07 19:32 ` Kevin Darbyshire-Bryant
2015-11-08 16:29 ` Dave Taht
2015-11-11 10:23 ` Kevin Darbyshire-Bryant [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56431715.7030902@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@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