NTPsec

b-ntpsec-72-hour-stats

Report generated: Thu Jul 18 02:11:42 2019 UTC
Start Time: Mon Jul 15 02:11:14 2019 UTC
End Time: Thu Jul 18 02:11:14 2019 UTC
Report published: Wed Jul 17 19:13:05 2019 PDT
Report Period: 3.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 -4.744 -1.023 -0.760 0.008 0.860 1.185 4.194 1.620 2.208 0.504 0.017 µs -3.477 10.43
Local Clock Frequency Offset -6.242 -6.240 -6.211 -5.958 -5.789 -5.783 -5.782 0.422 0.457 0.131 -5.977 ppm -1.025e+05 4.803e+06

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 103.000 129.000 152.000 231.000 514.000 724.000 3,127.000 362.000 595.000 137.544 265.885 ns 9.391 104.6

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 0.023 0.033 0.039 0.096 0.295 0.778 10.663 0.256 0.745 0.287 0.139 ppb 19.3 543.5

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 -4.744 -1.023 -0.760 0.008 0.860 1.185 4.194 1.620 2.208 0.504 0.017 µs -3.477 10.43

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 -6.242 -6.240 -6.211 -5.958 -5.789 -5.783 -5.782 0.422 0.457 0.131 -5.977 ppm -1.025e+05 4.803e+06
Temp ZONE0 56.382 56.920 57.458 60.148 62.838 63.376 63.914 5.380 6.456 1.699 60.369 °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 5.000 6.000 6.000 9.000 12.000 12.000 12.000 6.000 6.000 1.643 9.179 nSat 110.1 567.5
TDOP 0.510 0.550 0.610 0.880 1.550 2.180 2.980 0.940 1.630 0.323 0.953 15.37 62.68

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 162.213.2.253

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.213.2.253 -2.206 -2.176 -1.925 -1.225 -0.763 -0.606 -0.527 1.162 1.570 0.345 -1.266 ms -116.2 616.6

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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 -2.680 -2.497 -2.325 -1.659 -1.265 -1.110 -0.947 1.061 1.387 0.326 -1.705 ms -260.5 1750

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 192.168.1.10

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -174.844 -18.953 9.754 74.198 159.453 187.575 268.934 149.699 206.528 44.960 71.845 µs 2.254 7.068

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 192.168.1.12

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -425.364 28.401 81.340 182.859 240.147 278.651 549.783 158.807 250.250 52.249 169.910 µs 17.41 57.98

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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 -2.757 -2.510 -2.202 -1.588 -1.205 -1.078 -0.839 0.998 1.432 0.315 -1.640 ms -258.3 1734

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -7.663 -6.930 -6.345 -4.950 -3.740 -2.448 -1.651 2.605 4.481 0.824 -4.987 ms -371.5 2768

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) -507.190 -431.947 -416.033 -367.678 -318.062 -297.499 -247.114 97.971 134.448 30.089 -368.260 ms -2360 3.177e+04

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(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -4.745 -1.028 -0.761 0.009 0.861 1.186 4.195 1.622 2.214 0.505 0.016 µs -3.501 10.54

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 162.213.2.253

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.213.2.253 0.000 0.133 0.239 0.760 9.119 20.745 106.154 8.880 20.612 9.610 2.991 ms 7.169 78.75

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.000 0.153 0.233 0.737 8.871 15.119 115.869 8.638 14.966 6.295 2.668 ms 11.29 204.5

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 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.000 0.019 0.043 0.190 8.608 9.099 181.101 8.564 9.080 5.076 1.380 ms 14.51 429.3

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 192.168.1.12

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 0.000 0.023 0.051 0.520 8.707 56.763 80.399 8.656 56.740 7.977 2.466 ms 4.144 33.74

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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.000 0.161 0.229 0.657 9.148 14.743 159.935 8.919 14.582 7.234 2.711 ms 12.18 251.9

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 0.000 0.513 1.006 4.501 32.377 47.182 84.302 31.371 46.670 10.801 9.330 ms 1.739 8.216

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.000 4.612 6.201 11.674 23.201 30.614 80.344 17.001 26.002 5.470 12.834 ms 7.929 28.89

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(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.000 0.087 0.115 0.230 0.568 0.897 5.351 0.453 0.810 0.179 0.273 µs 7.743 113.6

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 -6.242 -6.240 -6.211 -5.958 -5.789 -5.783 -5.782 0.422 0.457 0.131 -5.977 ppm -1.025e+05 4.803e+06
Local Clock Time Offset -4.744 -1.023 -0.760 0.008 0.860 1.185 4.194 1.620 2.208 0.504 0.017 µs -3.477 10.43
Local RMS Frequency Jitter 0.023 0.033 0.039 0.096 0.295 0.778 10.663 0.256 0.745 0.287 0.139 ppb 19.3 543.5
Local RMS Time Jitter 103.000 129.000 152.000 231.000 514.000 724.000 3,127.000 362.000 595.000 137.544 265.885 ns 9.391 104.6
Server Jitter 162.213.2.253 0.000 0.133 0.239 0.760 9.119 20.745 106.154 8.880 20.612 9.610 2.991 ms 7.169 78.75
Server Jitter 169.229.128.134 0.000 0.153 0.233 0.737 8.871 15.119 115.869 8.638 14.966 6.295 2.668 ms 11.29 204.5
Server Jitter 192.168.1.10 0.000 0.019 0.043 0.190 8.608 9.099 181.101 8.564 9.080 5.076 1.380 ms 14.51 429.3
Server Jitter 192.168.1.12 0.000 0.023 0.051 0.520 8.707 56.763 80.399 8.656 56.740 7.977 2.466 ms 4.144 33.74
Server Jitter 216.218.192.202 0.000 0.161 0.229 0.657 9.148 14.743 159.935 8.919 14.582 7.234 2.711 ms 12.18 251.9
Server Jitter 76.14.161.109 0.000 0.513 1.006 4.501 32.377 47.182 84.302 31.371 46.670 10.801 9.330 ms 1.739 8.216
Server Jitter SHM(0) 0.000 4.612 6.201 11.674 23.201 30.614 80.344 17.001 26.002 5.470 12.834 ms 7.929 28.89
Server Jitter SHM(1) 0.000 0.087 0.115 0.230 0.568 0.897 5.351 0.453 0.810 0.179 0.273 µs 7.743 113.6
Server Offset 162.213.2.253 -2.206 -2.176 -1.925 -1.225 -0.763 -0.606 -0.527 1.162 1.570 0.345 -1.266 ms -116.2 616.6
Server Offset 169.229.128.134 -2.680 -2.497 -2.325 -1.659 -1.265 -1.110 -0.947 1.061 1.387 0.326 -1.705 ms -260.5 1750
Server Offset 192.168.1.10 -174.844 -18.953 9.754 74.198 159.453 187.575 268.934 149.699 206.528 44.960 71.845 µs 2.254 7.068
Server Offset 192.168.1.12 -425.364 28.401 81.340 182.859 240.147 278.651 549.783 158.807 250.250 52.249 169.910 µs 17.41 57.98
Server Offset 216.218.192.202 -2.757 -2.510 -2.202 -1.588 -1.205 -1.078 -0.839 0.998 1.432 0.315 -1.640 ms -258.3 1734
Server Offset 76.14.161.109 -7.663 -6.930 -6.345 -4.950 -3.740 -2.448 -1.651 2.605 4.481 0.824 -4.987 ms -371.5 2768
Server Offset SHM(0) -507.190 -431.947 -416.033 -367.678 -318.062 -297.499 -247.114 97.971 134.448 30.089 -368.260 ms -2360 3.177e+04
Server Offset SHM(1) -4.745 -1.028 -0.761 0.009 0.861 1.186 4.195 1.622 2.214 0.505 0.016 µs -3.501 10.54
TDOP 0.510 0.550 0.610 0.880 1.550 2.180 2.980 0.940 1.630 0.323 0.953 15.37 62.68
Temp ZONE0 56.382 56.920 57.458 60.148 62.838 63.376 63.914 5.380 6.456 1.699 60.369 °C
nSats 5.000 6.000 6.000 9.000 12.000 12.000 12.000 6.000 6.000 1.643 9.179 nSat 110.1 567.5
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!