How is the MTR scale calculated?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
When pressing "D" within MTR, one sees a "Last n pings" side-scrolling output. At the bottom is a scale with the different max-times. I understand how this relates to the scrolling data.
Scale: .:1 ms 1:4 ms 2:10 ms 3:17 ms a:28 ms b:40 ms c:54 ms >
How is this scale calculated? Periodically, it will change to reflect, I assume, new data. My guess is that it has to do with distributions of response times and that each level would represent a certain percentage.
I'd like to be able to look at the scale and say "95% of packets are returned within 28ms" for example.
How is the scale arrived at?
networking
asked Nov 14 at 8:07
Philip
1062
migrated from serverfault.com Nov 18 at 22:19
This question came from our site for system and network administrators.
add a comment |
up vote
1
down vote
favorite
When pressing "D" within MTR, one sees a "Last n pings" side-scrolling output. At the bottom is a scale with the different max-times. I understand how this relates to the scrolling data.
Scale: .:1 ms 1:4 ms 2:10 ms 3:17 ms a:28 ms b:40 ms c:54 ms >
How is this scale calculated? Periodically, it will change to reflect, I assume, new data. My guess is that it has to do with distributions of response times and that each level would represent a certain percentage.
I'd like to be able to look at the scale and say "95% of packets are returned within 28ms" for example.
How is the scale arrived at?
networking
asked Nov 14 at 8:07
Philip
1062
migrated from serverfault.com Nov 18 at 22:19
This question came from our site for system and network administrators.
1
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
1
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When pressing "D" within MTR, one sees a "Last n pings" side-scrolling output. At the bottom is a scale with the different max-times. I understand how this relates to the scrolling data.
Scale: .:1 ms 1:4 ms 2:10 ms 3:17 ms a:28 ms b:40 ms c:54 ms >
How is this scale calculated? Periodically, it will change to reflect, I assume, new data. My guess is that it has to do with distributions of response times and that each level would represent a certain percentage.
I'd like to be able to look at the scale and say "95% of packets are returned within 28ms" for example.
How is the scale arrived at?
networking
asked Nov 14 at 8:07
Philip
1062
When pressing "D" within MTR, one sees a "Last n pings" side-scrolling output. At the bottom is a scale with the different max-times. I understand how this relates to the scrolling data.
Scale: .:1 ms 1:4 ms 2:10 ms 3:17 ms a:28 ms b:40 ms c:54 ms >
How is this scale calculated? Periodically, it will change to reflect, I assume, new data. My guess is that it has to do with distributions of response times and that each level would represent a certain percentage.
I'd like to be able to look at the scale and say "95% of packets are returned within 28ms" for example.
How is the scale arrived at?
networking
networking
asked Nov 14 at 8:07
Philip
1062
asked Nov 14 at 8:07
Philip
1062
asked Nov 14 at 8:07
Philip
1062
asked Nov 14 at 8:07
Philip
1062
asked Nov 14 at 8:07
Philip
1062
1062
migrated from serverfault.com Nov 18 at 22:19
This question came from our site for system and network administrators.
migrated from serverfault.com Nov 18 at 22:19
This question came from our site for system and network administrators.
1
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
1
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32
add a comment |
1
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
1
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32
1
1
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
1
1
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
As far as I understand the source it is a square law.
Experimentally, with 7 scale items
- take the longest ping time
- take the square root and divide by 7² (for instance 166ms/49=3.388)
- then items for N=1..6 are N²*3.388
Take in account roundoff errors, for instance the displayed 166ms could be 165.5...
answered Nov 18 at 23:20
xenoid
2,5881724
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As far as I understand the source it is a square law.
Experimentally, with 7 scale items
- take the longest ping time
- take the square root and divide by 7² (for instance 166ms/49=3.388)
- then items for N=1..6 are N²*3.388
Take in account roundoff errors, for instance the displayed 166ms could be 165.5...
answered Nov 18 at 23:20
xenoid
2,5881724
add a comment |
up vote
0
down vote
As far as I understand the source it is a square law.
Experimentally, with 7 scale items
- take the longest ping time
- take the square root and divide by 7² (for instance 166ms/49=3.388)
- then items for N=1..6 are N²*3.388
Take in account roundoff errors, for instance the displayed 166ms could be 165.5...
answered Nov 18 at 23:20
xenoid
2,5881724
add a comment |
up vote
0
down vote
up vote
0
down vote
As far as I understand the source it is a square law.
Experimentally, with 7 scale items
- take the longest ping time
- take the square root and divide by 7² (for instance 166ms/49=3.388)
- then items for N=1..6 are N²*3.388
Take in account roundoff errors, for instance the displayed 166ms could be 165.5...
answered Nov 18 at 23:20
xenoid
2,5881724
As far as I understand the source it is a square law.
Experimentally, with 7 scale items
- take the longest ping time
- take the square root and divide by 7² (for instance 166ms/49=3.388)
- then items for N=1..6 are N²*3.388
Take in account roundoff errors, for instance the displayed 166ms could be 165.5...
answered Nov 18 at 23:20
xenoid
2,5881724
answered Nov 18 at 23:20
xenoid
2,5881724
answered Nov 18 at 23:20
xenoid
2,5881724
answered Nov 18 at 23:20
xenoid
2,5881724
2,5881724
add a comment |
add a comment |
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%2funix.stackexchange.com%2fquestions%2f482619%2fhow-is-the-mtr-scale-calculated%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
1
Look at the source.
– Ipor Sircer
Nov 14 at 8:23
1
Thank you for that, @IporSircer. I can understand RTFM, but RTFSC is a bit much.
– Philip
Nov 14 at 8:32