On Sat, Sep 10, 2011 at 10:45:55AM -0700, Bill Unruh wrote: > There are two separate problems in your system that have been noticed. The > first is that your system hops from one server to other, and sometimes refuses > to use either, because of the discrepancy in the times delivered by the > servers. The second is that large variance in the calculation of the slopeof > the system and computed by chrony. The second may be due to the > computer itself-- the hardware, the software you > are running, or a bug in chrony. The first is a problem with your time > servers it would seem. The second it would seem a problem with your > system. IS it the large number of realtime threads? To find out run > without that > pprogram for a while. Is it hardware or chrony?
My guess would be that the first problem is caused by the second problem. The sources are randomly marked as falsetickers due to the large variations in offset and chrony is forced to reselect. >From the older measurements log it seems that peer delay is stable at ms level. If the problem was that chrony is often preempted, I'd expect the peer delay to be much worse. Maybe this would show that it's not the case: $ grep ctxt /proc/`pidof chronyd`/status voluntary_ctxt_switches: 307234 nonvoluntary_ctxt_switches: 2134 -- Miroslav Lichvar --- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
