What does jitter have to do with a network connection being bad?
Someone told me that jitter is defined as how much the return time in ms of an ICMP is varying:
Pinging Some host [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=66ms TTL=122
Reply from x.x.x.x: bytes=32 time=68ms TTL=122
Reply from x.x.x.x: bytes=32 time=63ms TTL=122
Reply from x.x.x.x: bytes=32 time=67ms TTL=122
The above ping request offers little jitter...if the time in ms differed more wildly it would have a high rate of jitter.
networking jitter
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
add a comment |
Someone told me that jitter is defined as how much the return time in ms of an ICMP is varying:
Pinging Some host [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=66ms TTL=122
Reply from x.x.x.x: bytes=32 time=68ms TTL=122
Reply from x.x.x.x: bytes=32 time=63ms TTL=122
Reply from x.x.x.x: bytes=32 time=67ms TTL=122
The above ping request offers little jitter...if the time in ms differed more wildly it would have a high rate of jitter.
networking jitter
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
add a comment |
Someone told me that jitter is defined as how much the return time in ms of an ICMP is varying:
Pinging Some host [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=66ms TTL=122
Reply from x.x.x.x: bytes=32 time=68ms TTL=122
Reply from x.x.x.x: bytes=32 time=63ms TTL=122
Reply from x.x.x.x: bytes=32 time=67ms TTL=122
The above ping request offers little jitter...if the time in ms differed more wildly it would have a high rate of jitter.
networking jitter
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
Someone told me that jitter is defined as how much the return time in ms of an ICMP is varying:
Pinging Some host [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=66ms TTL=122
Reply from x.x.x.x: bytes=32 time=68ms TTL=122
Reply from x.x.x.x: bytes=32 time=63ms TTL=122
Reply from x.x.x.x: bytes=32 time=67ms TTL=122
The above ping request offers little jitter...if the time in ms differed more wildly it would have a high rate of jitter.
networking jitter
networking jitter
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
asked Jan 20 at 21:53
leeand00leeand00
6,6242783145
6,6242783145
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
High jitter implies that there is some random or intermittent component between you and your endpoint that is causing packets to be retransmitted or otherwise delayed.
For example a collision on a wifi connection would cause the packet to be lost and then it would need to be retransmitted. This would cause a random delay of some number of milliseconds as the transmitter would pause briefly to ensure "clear" air in order to make sure that the packet transmits cleanly. If another device causes another collision then packets get delayed further.
These kinds of "expected noisy" networks that actively detect and work around a collision are generally fault tolerant, but depending on how many devices are fighting for air time there can be a significant delay in a successful transmission.
This is one of the many causes of jitter, and every link can have different properties.
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396404%2fwhat-does-jitter-have-to-do-with-a-network-connection-being-bad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
High jitter implies that there is some random or intermittent component between you and your endpoint that is causing packets to be retransmitted or otherwise delayed.
For example a collision on a wifi connection would cause the packet to be lost and then it would need to be retransmitted. This would cause a random delay of some number of milliseconds as the transmitter would pause briefly to ensure "clear" air in order to make sure that the packet transmits cleanly. If another device causes another collision then packets get delayed further.
These kinds of "expected noisy" networks that actively detect and work around a collision are generally fault tolerant, but depending on how many devices are fighting for air time there can be a significant delay in a successful transmission.
This is one of the many causes of jitter, and every link can have different properties.
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
add a comment |
High jitter implies that there is some random or intermittent component between you and your endpoint that is causing packets to be retransmitted or otherwise delayed.
For example a collision on a wifi connection would cause the packet to be lost and then it would need to be retransmitted. This would cause a random delay of some number of milliseconds as the transmitter would pause briefly to ensure "clear" air in order to make sure that the packet transmits cleanly. If another device causes another collision then packets get delayed further.
These kinds of "expected noisy" networks that actively detect and work around a collision are generally fault tolerant, but depending on how many devices are fighting for air time there can be a significant delay in a successful transmission.
This is one of the many causes of jitter, and every link can have different properties.
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
add a comment |
High jitter implies that there is some random or intermittent component between you and your endpoint that is causing packets to be retransmitted or otherwise delayed.
For example a collision on a wifi connection would cause the packet to be lost and then it would need to be retransmitted. This would cause a random delay of some number of milliseconds as the transmitter would pause briefly to ensure "clear" air in order to make sure that the packet transmits cleanly. If another device causes another collision then packets get delayed further.
These kinds of "expected noisy" networks that actively detect and work around a collision are generally fault tolerant, but depending on how many devices are fighting for air time there can be a significant delay in a successful transmission.
This is one of the many causes of jitter, and every link can have different properties.
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
High jitter implies that there is some random or intermittent component between you and your endpoint that is causing packets to be retransmitted or otherwise delayed.
For example a collision on a wifi connection would cause the packet to be lost and then it would need to be retransmitted. This would cause a random delay of some number of milliseconds as the transmitter would pause briefly to ensure "clear" air in order to make sure that the packet transmits cleanly. If another device causes another collision then packets get delayed further.
These kinds of "expected noisy" networks that actively detect and work around a collision are generally fault tolerant, but depending on how many devices are fighting for air time there can be a significant delay in a successful transmission.
This is one of the many causes of jitter, and every link can have different properties.
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
answered Jan 20 at 22:31
Mokubai♦Mokubai
57.8k16139157
57.8k16139157
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396404%2fwhat-does-jitter-have-to-do-with-a-network-connection-being-bad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
