Re: Measuring clock offset results
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZLfwaFIdUUkVZFl9@localhost> |
On Wed, Jul 12, 2023 at 09:52:11AM -0700, Thangalin wrote: > https://ibb.co/album/1Z824p > > Are there any other ways we could help chronyd stay below 20 microseconds > (e.g., optimized build) that may have been overlooked (besides using GPIO)? If you zoom on those spikes and see that they are just single samples, it's probably not an error of the clock, but rather a measurement error (e.g. due to interrupt delays). You should implement some filtering in your program, e.g. use the median value from a number of consecutive samples (e.g. 5). That's what both ntpd and chronyd are doing with the data they get. -- Miroslav Lichvar -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]