From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Graph of bloat
Date: Thu, 09 Jul 2015 12:08:57 +0200 [thread overview]
Message-ID: <559E4839.6060308@gmail.com> (raw)
In-Reply-To: <CAA93jw4uG3fNJR=GEf=XcATyX6_Lvt-_xns7kE-OFF7HwTJC8A@mail.gmail.com>
On 08/07/15 18:32, Dave Taht wrote:
> Judging from that graphic... I don't think huff and puff was designed
> for the bufferbloated era! so the question remains, in hal's tests,
> did ntp adjust the clock backwards?
Dave,
No, ntpd did not adjust the time backwards.
What's going on in that graph is that it shows the different approach
that Google has taken to leap second insertion relative to ntpd's
implementation (which aligns with the standard).
Ntpd inserts a leap second by having the last UTC minute of the last day
of (in this case) June 30th last for 61 seconds rather than 60. The
extra second is number 60, after seconds 0 through 59. This is plotted
on the x axis.
The time reported by the Google server is compared to this on the y
axis. 10 hours prior to UTC midnight they slow down the clock by
1/72000, such that at the end of those 72000 seconds (20 hours) one more
"real" second will have passed than is reflected in the time reported by
the clock.
So obviously this means that during the 10 hours prior to UTC midnight
an offset is gradually built up between the Google servers and the rest
of the world, reaching half a second just prior to midnight. After the
leap second insertion on the standard server the sign of the offset is
inverted and the offset between the two begins to decline. 10 hours
after UTC midnight the Google servers return the rate of their clocks to
the normal "1 second per second" rate.
Anyway: Hal shared this because of the artifacts below the main graph
and he posits (quite reasonably) that this was due to bufferbloat.
Jan
next prev parent reply other threads:[~2015-07-09 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 10:23 Hal Murray
2015-07-08 15:55 ` Dave Taht
2015-07-08 16:11 ` Jan Ceuleers
2015-07-08 16:29 ` Jan Ceuleers
2015-07-08 19:09 ` Alan Jenkins
2015-07-08 16:32 ` Dave Taht
2015-07-09 10:08 ` Jan Ceuleers [this message]
2015-07-08 17:53 ` Rich Brown
2015-07-09 10:07 ` Hal Murray
2015-07-09 10:55 ` Sebastian Moeller
2015-07-09 18:27 ` Hal Murray
2015-07-09 15:08 ` Dave Taht
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=559E4839.6060308@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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