NTPsec

tock

Report generated: Sun Dec 8 12:15:51 2019 UTC
Start Time: Sat Dec 7 12:15:50 2019 UTC
End Time: Sun Dec 8 12:15:50 2019 UTC
Report Period: 1.0 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -2,064.000 -804.000 -375.000 5.000 297.000 422.000 711.000 672.000 1,226.000 233.898 -12.054 ns -6.15 28.16
Local Clock Frequency Offset -21.893 -21.892 -21.891 -21.880 -21.834 -21.833 -21.833 0.057 0.059 0.021 -21.870 ppm -1.147e+09 1.2e+12

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 98.000 120.000 138.000 197.000 280.000 332.000 421.000 142.000 212.000 44.607 202.318 ns 55.45 244

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 18.000 26.000 30.000 42.000 80.000 415.000 1,002.000 50.000 389.000 69.130 54.625 10e-12 7.343 71.85

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -2,064.000 -804.000 -375.000 5.000 297.000 422.000 711.000 672.000 1,226.000 233.898 -12.054 ns -6.15 28.16

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -21.893 -21.892 -21.891 -21.880 -21.834 -21.833 -21.833 0.057 0.059 0.021 -21.870 ppm -1.147e+09 1.2e+12
Temp ZONE0 51.608 52.095 52.582 53.556 54.530 55.017 55.504 1.948 2.922 0.644 53.470 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 4.000 5.000 5.000 7.000 8.000 9.000 9.000 3.000 4.000 0.955 6.544 nSat 218.2 1386
TDOP 1.000 1.080 1.190 1.670 4.480 6.270 11.420 3.290 5.190 1.184 2.065 5.675 28.02

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 10.4.2.51

peer offset 10.4.2.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.4.2.51 -17.386 -12.359 -8.684 2.075 11.532 14.083 20.046 20.216 26.442 6.055 2.055 µs -2.493 6.085

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.4.2.53

peer offset 10.4.2.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.4.2.53 -122.640 -93.413 -85.873 -69.977 -58.743 -53.698 -48.042 27.130 39.715 8.083 -70.579 µs -951.7 9573

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset PPS(0)

peer offset PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset PPS(0) -2,065.000 -805.000 -376.000 6.000 298.000 423.000 712.000 674.000 1,228.000 234.576 -12.029 ns -6.136 28

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -18.193 -12.881 -8.797 5.219 16.031 19.248 24.874 24.829 32.130 7.371 4.522 ms -1.477 3.955

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.4.2.51

peer jitter 10.4.2.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.4.2.51 1.966 2.790 4.124 9.284 19.580 24.718 51.572 15.456 21.928 5.130 10.398 µs 5.397 19.35

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.4.2.53

peer jitter 10.4.2.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.4.2.53 2.646 4.392 6.977 16.762 28.500 36.052 54.170 21.523 31.660 6.723 16.993 µs 8.828 27.95

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 40.000 80.000 104.000 199.000 398.000 531.000 1,133.000 294.000 451.000 96.363 219.210 ns 7.701 31.64

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.716 1.354 1.898 3.962 7.616 10.156 16.534 5.718 8.802 1.836 4.281 ms 7.564 25.84

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -21.893 -21.892 -21.891 -21.880 -21.834 -21.833 -21.833 0.057 0.059 0.021 -21.870 ppm -1.147e+09 1.2e+12
Local Clock Time Offset -2,064.000 -804.000 -375.000 5.000 297.000 422.000 711.000 672.000 1,226.000 233.898 -12.054 ns -6.15 28.16
Local RMS Frequency Jitter 18.000 26.000 30.000 42.000 80.000 415.000 1,002.000 50.000 389.000 69.130 54.625 10e-12 7.343 71.85
Local RMS Time Jitter 98.000 120.000 138.000 197.000 280.000 332.000 421.000 142.000 212.000 44.607 202.318 ns 55.45 244
Server Jitter 10.4.2.51 1.966 2.790 4.124 9.284 19.580 24.718 51.572 15.456 21.928 5.130 10.398 µs 5.397 19.35
Server Jitter 10.4.2.53 2.646 4.392 6.977 16.762 28.500 36.052 54.170 21.523 31.660 6.723 16.993 µs 8.828 27.95
Server Jitter PPS(0) 40.000 80.000 104.000 199.000 398.000 531.000 1,133.000 294.000 451.000 96.363 219.210 ns 7.701 31.64
Server Jitter SHM(0) 0.716 1.354 1.898 3.962 7.616 10.156 16.534 5.718 8.802 1.836 4.281 ms 7.564 25.84
Server Offset 10.4.2.51 -17.386 -12.359 -8.684 2.075 11.532 14.083 20.046 20.216 26.442 6.055 2.055 µs -2.493 6.085
Server Offset 10.4.2.53 -122.640 -93.413 -85.873 -69.977 -58.743 -53.698 -48.042 27.130 39.715 8.083 -70.579 µs -951.7 9573
Server Offset PPS(0) -2,065.000 -805.000 -376.000 6.000 298.000 423.000 712.000 674.000 1,228.000 234.576 -12.029 ns -6.136 28
Server Offset SHM(0) -18.193 -12.881 -8.797 5.219 16.031 19.248 24.874 24.829 32.130 7.371 4.522 ms -1.477 3.955
TDOP 1.000 1.080 1.190 1.670 4.480 6.270 11.420 3.290 5.190 1.184 2.065 5.675 28.02
Temp ZONE0 51.608 52.095 52.582 53.556 54.530 55.017 55.504 1.948 2.922 0.644 53.470 °C
nSats 4.000 5.000 5.000 7.000 8.000 9.000 9.000 3.000 4.000 0.955 6.544 nSat 218.2 1386
Summary as CSV file

Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!