From: Alex Burr <ajb44.geo@yahoo.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fw: Measuring Latency
Date: Sun, 14 Sep 2014 10:51:44 -0700 [thread overview]
Message-ID: <1410717104.12610.YahooMailNeo@web122503.mail.ne1.yahoo.com> (raw)
In-Reply-To: <1410691150.20919.YahooMailNeo@web122503.mail.ne1.yahoo.com>
Oops, intended to CC the list...
> On Sunday, September 14, 2014 11:39 AM, Alex Burr <ajb44.geo@yahoo.com> wrote:
> >
>
>
>
>
> On Sunday, September 14, 2014 12:32 AM, Jonathan Morton
> <chromatix99@gmail.com> wrote:
>
>
>>
>>
>> To expand on this: to measure one-way delay, you would need finely
> synchronised clocks (to within a
>> couple of ms) at both ends. The average consumer doesn't have that
> sort of setup - not even if they
>> happen to use NTP. So it's not a goal worth pursuing at this level -
> save it for scientific
>> Investigations, where the necessary effort and equipment can be made
> available.
>
>
> This is true for absolute one way delay. But since we are interested in the
> variation
> with load, it's actually easier. When you take the difference of two delays,
> the synchronisation offset cancels out, so you are left with just the drift.
> That may still be an insurmountable problem, but I would suggest at least
> putting timestamps in the packets, even if you don't estimate one-way delay
> up-front. That way people can try and get clever with clients later, without
> having to change the server.
>
> Alex
>
prev parent reply other threads:[~2014-09-14 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 19:41 [Bloat] " 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
[not found] ` <1410691150.20919.YahooMailNeo@web122503.mail.ne1.yahoo.com>
2014-09-14 17:51 ` Alex Burr [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/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=1410717104.12610.YahooMailNeo@web122503.mail.ne1.yahoo.com \
--to=ajb44.geo@yahoo.com \
--cc=bloat@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