Yo Achim!
On Mon, 19 Sep 2016 20:09:04 +0200
Achim Gratz wrote:
> Oh, I see it now. You're plotting days-hh:mm, not hh-mm:ss as I
> assumed initially.
I just pushed a change to the x label. From "Time" to "Time (dd-hh:mm)".
Does that resolve the confusion?
RGDS
GARY
---
Yo Achim!
On Mon, 19 Sep 2016 20:09:04 +0200
Achim Gratz wrote:
> Gary E. Miller writes:
> >> You 've made this argument before, but I think it's circular
> >> reasoning.
> >
> > Really? I think the data is very clear, you can optimize for time
> > or for frequency.
>
> No, I still think y
Gary E. Miller writes:
>> You 've made this argument before, but I think it's circular
>> reasoning.
>
> Really? I think the data is very clear, you can optimize for time
> or for frequency.
No, I still think you're misinterpreting it. The only reason you see
that apparent tradeoff is that once
Yo Achim!
On Fri, 16 Sep 2016 20:17:50 +0200
Achim Gratz wrote:
> Gary E. Miller writes:
> > Poll=2s is still the bast for this hardware, but there is a little
> > tradeoff between offset and jitter. Since NTP is about time, not
> > frequency, we go with the best time.
>
> You 've made this
Gary E. Miller writes:
> Poll=2s is still the bast for this hardware, but there is a little
> tradeoff between offset and jitter. Since NTP is about time, not
> frequency, we go with the best time.
You 've made this argument before, but I think it's circular reasoning.
You make the local clock fo
Yo All!
I have some solid results on minpoll=maxpoll=2. That gives a poll time
of 4 seconds. This results set after about 43 hours of run time. Eric
delegated me the task to fix for minnpoll=maxpoll=0. On my list to fix
early next week.
First, the bbad news. On a Raspberry Pi 3B, with
Yo All!
I have some solid results on minpoll=maxpoll=1. That gives a
poll time of 2 seconds. When minpoll=maxpoll=0 works Ill be testing
that. UNtil thne I'll be testing other values.
First, the good news. On a Raspberry Pi 3B, with Uputronics hat,
minpoll=maxpoll=1 is much better than minpo
