How to eliminate the delay in NTP synchronization?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite
1












Currently, I am doing a NTP time synchronization between two ubuntu pcs connected by a LAN cable. After I finish the setup, I find that the delay is around 0.170s (170ms), which is not acceptable since I expect a delay less than 30ms. What could be the reasons causing the delay? And how could I solve it?







share|improve this question




















  • how do you measure this delay?
    – pim
    Apr 24 at 9:17














up vote
2
down vote

favorite
1












Currently, I am doing a NTP time synchronization between two ubuntu pcs connected by a LAN cable. After I finish the setup, I find that the delay is around 0.170s (170ms), which is not acceptable since I expect a delay less than 30ms. What could be the reasons causing the delay? And how could I solve it?







share|improve this question




















  • how do you measure this delay?
    – pim
    Apr 24 at 9:17












up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





Currently, I am doing a NTP time synchronization between two ubuntu pcs connected by a LAN cable. After I finish the setup, I find that the delay is around 0.170s (170ms), which is not acceptable since I expect a delay less than 30ms. What could be the reasons causing the delay? And how could I solve it?







share|improve this question












Currently, I am doing a NTP time synchronization between two ubuntu pcs connected by a LAN cable. After I finish the setup, I find that the delay is around 0.170s (170ms), which is not acceptable since I expect a delay less than 30ms. What could be the reasons causing the delay? And how could I solve it?









share|improve this question











share|improve this question




share|improve this question










asked Apr 24 at 8:11









Teddy_NTU

132




132











  • how do you measure this delay?
    – pim
    Apr 24 at 9:17
















  • how do you measure this delay?
    – pim
    Apr 24 at 9:17















how do you measure this delay?
– pim
Apr 24 at 9:17




how do you measure this delay?
– pim
Apr 24 at 9:17










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










I assume you use ntpq, which gives delay in milliseconds. 0.170 in the delay column of ntpq -p means a delay of 0.170ms, not 0.170 seconds.



0.170ms is a reasonable delay over a switched ethernet. 170ms does not make a lot of sense.



Explanation of the output is given in the ntpq documentation:




peers

Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.




My formatting.






share|improve this answer
















  • 1




    Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
    – Teddy_NTU
    Apr 25 at 5:57










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027712%2fhow-to-eliminate-the-delay-in-ntp-synchronization%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










I assume you use ntpq, which gives delay in milliseconds. 0.170 in the delay column of ntpq -p means a delay of 0.170ms, not 0.170 seconds.



0.170ms is a reasonable delay over a switched ethernet. 170ms does not make a lot of sense.



Explanation of the output is given in the ntpq documentation:




peers

Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.




My formatting.






share|improve this answer
















  • 1




    Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
    – Teddy_NTU
    Apr 25 at 5:57














up vote
0
down vote



accepted










I assume you use ntpq, which gives delay in milliseconds. 0.170 in the delay column of ntpq -p means a delay of 0.170ms, not 0.170 seconds.



0.170ms is a reasonable delay over a switched ethernet. 170ms does not make a lot of sense.



Explanation of the output is given in the ntpq documentation:




peers

Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.




My formatting.






share|improve this answer
















  • 1




    Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
    – Teddy_NTU
    Apr 25 at 5:57












up vote
0
down vote



accepted







up vote
0
down vote



accepted






I assume you use ntpq, which gives delay in milliseconds. 0.170 in the delay column of ntpq -p means a delay of 0.170ms, not 0.170 seconds.



0.170ms is a reasonable delay over a switched ethernet. 170ms does not make a lot of sense.



Explanation of the output is given in the ntpq documentation:




peers

Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.




My formatting.






share|improve this answer












I assume you use ntpq, which gives delay in milliseconds. 0.170 in the delay column of ntpq -p means a delay of 0.170ms, not 0.170 seconds.



0.170ms is a reasonable delay over a switched ethernet. 170ms does not make a lot of sense.



Explanation of the output is given in the ntpq documentation:




peers

Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.




My formatting.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 24 at 10:16









vidarlo

7,12342140




7,12342140







  • 1




    Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
    – Teddy_NTU
    Apr 25 at 5:57












  • 1




    Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
    – Teddy_NTU
    Apr 25 at 5:57







1




1




Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
– Teddy_NTU
Apr 25 at 5:57




Oh my god. I think you are correct. I thought the unit of delay in ntpq -p is in seconds. Thank you very much.
– Teddy_NTU
Apr 25 at 5:57

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027712%2fhow-to-eliminate-the-delay-in-ntp-synchronization%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491