Matt Wagner wrote:
> I can't answer your full question; the jitter seems strange to me. A
> few thoughts, though:
>
> (You've got to love
> when a 4ms difference constitutes an outlier!)
Indeed, these servers look relatively healthy to me, given that with the
high delays you're getting an order of magnitude better offsets. While
you could get better performance, it's going to take ever-increasing
effort to get the next zeroes.
> - Blue's IP, 192.43.244.18, is not a conventional "non-routable"
> internal IP.
Of course not. That's not blue's IP; it's time.nist.gov.
> The delay amounts to about 14ms latency,
I don't see that. What I do see is that red and blue are not peers, so
we can't say a whole lot about how well they perform relative to each
other. Also, the jitter on darkcity is pretty high, but since it's
stratum one it may be dragging red up and down the block regarding its
own offset.
The only server these two have in common seems to be europium, and they
have virtually the same delay and offset to it, which is a good sign.
>
> Hope this helps!
> -- Matt (N1ZYY)
>
>
>>
>> Why does red not use the data from Blue?
>>
Probably because it selected darkcity, at a lower stratum.
>> What would cause Blue to have so much jitter when they are so close
>> together? Do I have something set wrong?
>>
See previous answer, i.e. because red selected darkcity, its own offset
has jitter that make blue look worse.
--
Jeff Woolsey {woolsey,[EMAIL PROTECTED],[EMAIL PROTECTED]
Nature abhors a straight antenna, a clean lens, and unused storage capacity.
"Delete! Delete! OK!" -Dr. Bronner on disk space management
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
