From: Jonathan Morton <chromatix99@gmail.com>
To: esr@thyrsus.com
Cc: bloat-devel@lists.bufferbloat.net,
Eric Raymond <esr@snark.thyrsus.com>,
Hal Murray <hmurray@megapathdsl.net>
Subject: Re: Preliminary results of using GPS to look for clock skew
Date: Thu, 22 Sep 2011 05:24:15 +0300 [thread overview]
Message-ID: <D61AB68F-2055-4D1D-A71E-3C1F0AFD6BB1@gmail.com> (raw)
In-Reply-To: <20110922021137.GB21302@thyrsus.com>
On 22 Sep, 2011, at 5:11 am, Eric Raymond wrote:
>> 2) ReRun all tests under load (example: netperf -l 3600 -H the_router)
>
> I'll do this, for completeness, but I predict it's not going to make
> any measurable difference. The indications so far are that neither of
> the means of time delivery I have available to check are compute-bound
> or disk-I/O bound at any point in their delivery chains.
>
> So I think they're just going to shrug off any load short of
> machine-thrashing-its-guts-out. But part of the point of what I'm
> doing is that soon we'll have the test tools to know for *sure* that's
> true.
When the *network* is loaded, the latency to the NTP server changes. That is likely to confuse ntpd - it certainly did when I lived on an analogue modem.
- Jonathan Morton
next prev parent reply other threads:[~2011-09-22 2:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 23:02 Eric Raymond
2011-09-22 0:18 ` Dave Taht
2011-09-22 2:11 ` Eric Raymond
2011-09-22 2:24 ` Jonathan Morton [this message]
2011-09-22 2:29 ` Eric Raymond
2011-09-23 9:09 ` Jan Ceuleers
2011-09-23 9:38 ` Dave Taht
2011-09-23 12:10 ` Jan Ceuleers
2011-09-23 12:50 ` Rick
2011-09-24 14:50 ` Jan Ceuleers
2011-09-22 9:08 ` Dave Taht
2011-09-22 17:15 ` Rick Jones
2011-09-22 17:34 ` Dave Taht
2011-09-22 17:43 ` Rick Jones
2011-09-22 17:58 ` Dave Taht
2011-09-23 10:57 ` Aidan Williams
2011-09-23 10:10 ` Dave Taht
2011-09-23 9:09 ` Jan Ceuleers
2011-09-23 9:24 ` Jan Ceuleers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D61AB68F-2055-4D1D-A71E-3C1F0AFD6BB1@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=hmurray@megapathdsl.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