SCIENTIFIC-LINUX-USERS Archives

March 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Reply To:
Konstantin Olchanski <[log in to unmask]>
Date:
Fri, 11 Mar 2016 20:43:42 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
> 
> I confess that I have no real evidence on performance differences
> between NTPD and chronyd...
>

I do have some evidence.

chrony works better:

a) ntpd steps the time, some applications do not like that, chrony seems to always adjust time smoothly
b) on some special purpose machines ntpd fails to lock and sync the time (at all - probably
   because of a hardwired limit on maximum permitted time drift), chrony works okey
c) debug and diagnostics information from ntpd is impossible to understand, chronyc reports very well
   who we are locked on, what is the time difference, who's clock is running too fast/too slow,
   how well we are tracking, etc.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2