General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Neil Davies <neil.davies@pnsol.com>
Cc: Hal Murray <hmurray@megapathdsl.net>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Measuring Latency
Date: Sun, 14 Sep 2014 19:57:11 +0300	[thread overview]
Message-ID: <5CFDFA23-3212-4B78-8D9F-09B248AFBE4A@gmail.com> (raw)
In-Reply-To: <1AF70E51-A60F-47C1-AF90-9B1E6030227C@pnsol.com>


On 14 Sep, 2014, at 5:31 pm, Neil Davies wrote:

> This is not actually true - you can measure one-way delays without completely accurately synchronised clocks (they have to be reasonably precise, not accurate) - see CERN thesis at http://goo.gl/ss6EBq

I read the abstract of that, and came away with the distinct impression that I wouldn't learn anything from reading the rest of the paper.  Not that there *isn't* good information there, but that it's most likely not in a form that I can digest.

And that means it's probably impractical to implement on a consumer broadband test.  Timestamps - sure, why not - but I don't yet see what you could do with them.

> It is possible, with appropriate measurements, to construct arguments that make marketeers salivate (or the appropriate metaphor) - you can compare the relative effects of technology, location and instantaneous congestion. See slideshare at http://goo.gl/6vytmD

I'm sure those must be a different breed of marketing types than I have in mind.  There are major ISPs who claim that 3% packet loss "is not a fault" - on an idle wire line, not wireless, not congested.  They are all about sales and retention by brute force and semi-monopoly position, not by genuinely providing superior service.

Hence why we have to turn to the external consumer-oriented organisations, the speed-test sites among them.  They will have to serve as *our* marketing tool.

 - Jonathan Morton


  parent reply	other threads:[~2014-09-14 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 19:41 Hal Murray
2014-09-13 19:48 ` Sebastian Moeller
2014-09-13 23:32   ` Jonathan Morton
2014-09-14 14:31     ` Neil Davies
2014-09-14 16:55       ` Sebastian Moeller
2014-09-14 17:26         ` Neil Davies
2014-09-14 16:57       ` Jonathan Morton [this message]
     [not found]     ` <1410691150.20919.YahooMailNeo@web122503.mail.ne1.yahoo.com>
2014-09-14 17:51       ` [Bloat] Fw: " Alex Burr

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=5CFDFA23-3212-4B78-8D9F-09B248AFBE4A@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=hmurray@megapathdsl.net \
    --cc=neil.davies@pnsol.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