Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "David P. Reed" <dpreed@reed.com>
Cc: Greg White <g.white@CableLabs.com>,
	bloat <bloat@lists.bufferbloat.net>,
	"Livingood, Jason" <Jason_Livingood@cable.comcast.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	MUSCARIELLO Luca IMT/OLN <luca.muscariello@orange.com>
Subject: Re: [Cerowrt-devel] [Bloat]  DOCSIS 3+ recommendation?
Date: Fri, 20 Mar 2015 14:46:29 +0100	[thread overview]
Message-ID: <AE05F01C-567E-47F0-AA3C-BC22BB16F27F@gmx.de> (raw)
In-Reply-To: <e8b29dbd-287e-46bf-b9bd-66ae04e21a41@reed.com>

Hi David,

On Mar 20, 2015, at 14:31 , David P. Reed <dpreed@reed.com> wrote:

> The mystery in most users' minds is that ping at a time when there is no load does tell them anything at all about why the network connection will such when their kid is uploading to youtube.

	But it does, by giving a baseline to compare the ping tim under load against ;)

> 
> So giving them ping time is meaningless. 
> I think most network engineers think ping time is a useful measure of a badly bufferbloated system. It is not.
> 
> The only measure is ping time under maximum load of raw packets.

	Why raw packets? But yes I agree; I think “ping” in this discussion here is short hand for "latency measurement under load” which writes a bit unwieldy. The typical speed tests are almost there as they already perform (half of) the create maximum load requirement for the additional measurements we need (as well as already measuring unloaded latency, they all already report a “ping” number back, but that is best case RTT, so the baseline with which to compare the latency under load number (well obviously both numbers should be measured exactly the same)). Measuring latency under simultaneous saturation of both up- and downlink would be even better, but measuring it during simplex saturation should already give meaningful numbers.
	I think it would be great if speedtest sites could agree to measure and report such a number, so that end customers had data to base their ISP selection on (at least those fortunate few that actually have ISP choice…).

> 
> And that requires a way to test maximum load rtt.
> 
> There is no problem with that ... other than that to understand why and how that is relevant you have to understand Internet congestion control.  
> 
> Having had to testify before CRTC about this, I learned that most access providers (the Canadian ones) claim that such measurements are never made as a measure of quality, and that you can calculate expected latency by using Little's lemma from average throughput. And that dropped packets are the right measure of quality of service.
> 
> Ookla ping time  is useless in a context where even the "experts" wearing ties from the top grossing Internet firms are so confused. And maybe deliberately misleading on purpose... they had to be forced to provide any data they had about  congestion in their networks by a ruling during the proceeding and then responded that they had no data - they never measured queueing delay and disputed that it mattered. The proper measure of congestion was throughput.
> 
> I kid you not.
> 
> So Ookla ping time is useless against such public ignorance. 

	But, if people make their choice of (higher/ more expensive) service tiers dependent on its behavior at “capacity” as approximated by a speedtest latency under (full) load test that would make it much easier for ISPs to actually respond to it; even marketing can realize that this can be monetized ;)

Best Regards
	Sebastian


[...]

  reply	other threads:[~2015-03-20 13:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 20:35 [Cerowrt-devel] " Matt Taggart
2015-03-17 23:32 ` Valdis.Kletnieks
2015-03-18  4:34   ` David P. Reed
2015-03-18  6:26     ` Jonathan Morton
2015-03-18 19:38       ` JF Tremblay
2015-03-18 19:50         ` Jonathan Morton
2015-03-19 13:53           ` dpreed
2015-03-19 14:11             ` JF Tremblay
2015-03-19 15:38               ` dpreed
2015-03-19 15:40               ` Jim Gettys
2015-03-19 17:04                 ` Michael Richardson
2015-03-19 17:14                   ` Jonathan Morton
2015-03-19 17:11             ` Dave Taht
2015-03-19 19:58               ` [Cerowrt-devel] [Bloat] " Livingood, Jason
2015-03-19 20:29                 ` dpreed
2015-03-19 23:18                   ` Greg White
2015-03-20  8:18                     ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31                       ` David P. Reed
2015-03-20 13:46                         ` Sebastian Moeller [this message]
2015-03-20 14:05                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07                     ` Sebastian Moeller
2015-03-20 13:50                     ` [Cerowrt-devel] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36                       ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2015-03-30  7:06                         ` Jonathan Morton
2015-03-20 13:57                     ` [Cerowrt-devel] [Bloat] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08                       ` David P. Reed
2015-03-20 14:14                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48                           ` Matt Mathis
2015-03-20 18:04                         ` Valdis.Kletnieks
2015-03-20 13:48                 ` Jim Gettys
2015-03-20 14:11                   ` Livingood, Jason
2015-03-20 14:54                     ` Michael Welzl
2015-03-20 15:31                       ` Jim Gettys
2015-03-20 15:39                         ` Michael Welzl
2015-03-20 16:31                       ` Jonathan Morton
2015-03-20 20:59                         ` Michael Welzl
2015-03-20 23:47                           ` David P. Reed
2015-03-21  0:08                             ` Michael Welzl
2015-03-21  0:03                           ` David Lang
2015-03-21  0:13                             ` Steinar H. Gunderson
2015-03-21  0:25                               ` David Lang
2015-03-21  0:34                                 ` Jonathan Morton
2015-03-21  0:38                                   ` David Lang
2015-03-21  0:43                                     ` Jonathan Morton
2015-03-22  4:15                                 ` Michael Welzl
2015-03-21  0:15                             ` Michael Welzl
2015-03-21  0:29                               ` David Lang
2015-03-22  4:10                                 ` Michael Welzl
2015-03-20 18:14                     ` Jonathan Morton
2015-03-18  8:06     ` [Cerowrt-devel] " 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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AE05F01C-567E-47F0-AA3C-BC22BB16F27F@gmx.de \
    --to=moeller0@gmx.de \
    --cc=Jason_Livingood@cable.comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=g.white@CableLabs.com \
    --cc=luca.muscariello@orange.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