Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Jannie Hanekom" <jannie@hanekom.net>
To: "'Michael Richardson'" <mcr@sandelman.ca>
Cc: "'Sergey Fedorov'" <sfedorov@netflix.com>,
	"'Sebastian Moeller'" <moeller0@gmx.de>,
	"'Cake List'" <cake@lists.bufferbloat.net>,
	"'Make-Wifi-fast'" <make-wifi-fast@lists.bufferbloat.net>,
	"'bloat'" <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Make-wifi-fast] [Bloat]  dslreports is no longer free
Date: Sat, 2 May 2020 03:14:19 +0200	[thread overview]
Message-ID: <013601d6201f$04c7db50$0e5791f0$@hanekom.net> (raw)
In-Reply-To: <24457.1588370840@localhost>

Michael Richardson <mcr@sandelman.ca>:
> Does it find/use my nearest Netflix cache?

Thankfully, it appears so.  The DSLReports bloat test was interesting, but
the jitter on the ~240ms base latency from South Africa (and other parts of
the world) was significant enough that the figures returned were often
unreliable and largely unusable - at least in my experience.

Fast.com reports my unloaded latency as 4ms, my loaded latency as ~7ms and
mentions servers located in local cities.  I finally have a test I can share
with local non-technical people!

(Agreed, upload test would be nice, but this is a huge step forward from
what I had access to before.)

Jannie Hanekom


  parent reply	other threads:[~2020-05-02  1:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 16:44 [Cake] " Dave Taht
2020-05-01 19:34 ` [Cake] [Bloat] " Kenneth Porter
2020-05-01 19:54   ` Sebastian Moeller
2020-05-01 19:48 ` [Cake] " Sebastian Moeller
2020-05-01 20:09   ` [Bloat] " Sergey Fedorov
2020-05-01 21:11     ` [Cake] [Bloat] " Sebastian Moeller
2020-05-01 21:37       ` [Bloat] [Cake] " Sergey Fedorov
     [not found]       ` <mailman.191.1588369068.24343.bloat@lists.bufferbloat.net>
2020-05-01 23:59         ` [Cake] [Bloat] " Michael Richardson
     [not found]   ` <mailman.170.1588363787.24343.bloat@lists.bufferbloat.net>
2020-05-01 22:07     ` Michael Richardson
2020-05-01 23:35       ` [Bloat] [Cake] " Sergey Fedorov
2020-05-02  1:14       ` Jannie Hanekom [this message]
2020-05-02 16:37         ` [Cake] [Make-wifi-fast] [Bloat] " Benjamin Cronce
2020-05-02 16:52           ` Dave Taht
2020-05-02 17:38             ` David P. Reed
2020-05-02 19:00               ` Sergey Fedorov
2020-05-02 23:23                 ` David P. Reed
2020-05-03 15:31                 ` [Cake] fast.com quality David P. Reed
2020-05-03 15:37                   ` Dave Taht
2020-05-02 20:19               ` [Cake] [Make-wifi-fast] [Bloat] dslreports is no longer free Sebastian Moeller
2020-05-27  9:08   ` [Cake] " Matthew Ford
2020-05-27  9:28     ` [Cake] [Make-wifi-fast] " Toke Høiland-Jørgensen
2020-05-27  9:32     ` [Cake] " Sebastian Moeller
2020-05-03 15:06 [Cake] [Make-wifi-fast] " David P. Reed
2020-05-03 17:22 ` Dave Taht
2020-05-04 17:04 ` Sergey Fedorov
2020-05-05 21:02   ` David P. Reed
2020-05-06  8:19   ` Sebastian Moeller
2020-05-06  8:08 ` Sebastian Moeller

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='013601d6201f$04c7db50$0e5791f0$@hanekom.net' \
    --to=jannie@hanekom.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    --cc=moeller0@gmx.de \
    --cc=sfedorov@netflix.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