Re: ✘minpoll=maxpoll=4

Yo All! New data for poll=4 (16 Sec). Like before, all data is 90% bounds, run over 24 hours or more. Clearly the proper minpoll=maxpoll is important and non-trivial to find. Xeon: Local Clock Local Clock Local ClockPPS PPS Poll Freq Offset 90% Jitter 90% Stability

Re: ✘minpoll=maxpoll=2

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

Re: ✘minpoll=maxpoll=2

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. > >

Re: ✘minpoll=maxpoll=2

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