You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2024-11-17 22:19:57
- ThoughtBubble
- Member
- Registered: 2024-07-09
- Posts: 55
Reducing network latency
When I run "ping archlinux.org" on my Arch machine, this are the (approximate) stats I get
rtt min/avg/max/mdev = 140/200/270/30 ms
When I run the same command on another (non-Arch) machine, I get these stats (approximate)
rtt min/avg/max/mdev = 140/145/160/5 ms
I want to reduce this latency on my Arch machine. Where do I start?
Offline
#2 2024-11-17 22:50:40
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 20,411
Re: Reducing network latency
Don't use ping to measure latency beyond looking for gross problems?
Does the comparison of traceroute provide any additional information as to why the machines behave differently? You might find that the first hop is (or is not) the problem.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
#3 2024-11-17 23:03:14
- seth
- Member
- Registered: 2012-09-03
- Posts: 65,450
Re: Reducing network latency
Otherwise, if both systems are in the same LAN segment, compare "ping 8.8.8.8" and "ping -4n google.com" next to "ping -4 google.com"
Offline
#4 2024-11-23 19:27:15
- ThoughtBubble
- Member
- Registered: 2024-07-09
- Posts: 55
Re: Reducing network latency
Don't use ping to measure latency beyond looking for gross problems?
Does the comparison of traceroute provide any additional information as to why the machines behave differently? You might find that the first hop is (or is not) the problem.
You're right. The first hop is not the problem. It seems to lie on a hop between two countries, I think. I wonder why that is the case.
Otherwise, if both systems are in the same LAN segment, compare "ping 8.8.8.8" and "ping -4n google.com" next to "ping -4 google.com"
The difference is negligible, though Arch always seems to have slightly more latency
Last edited by ThoughtBubble (2024-11-23 19:29:06)
Offline
#5 2024-11-24 19:07:00
- seth
- Member
- Registered: 2012-09-03
- Posts: 65,450
Re: Reducing network latency
The first hop is not the problem. It seems to lie on a hop between two countries, I think. I wonder why that is the case.
Can you post the tracepath output?
The difference is negligible, though Arch always seems to have slightly more latency
negligible between the three ping variants or negligible compared between two LAN hosts (for all three ping variants)?
Wrt the previous:
Does the latency significantly differ between "ping archlinux.org" and "ping google.com"?
What about "ping heise.de"?
Offline
#6 2024-11-25 19:39:56
- ThoughtBubble
- Member
- Registered: 2024-07-09
- Posts: 55
Re: Reducing network latency
Can you post the tracepath output?
Before I post the tracepath outputs, should I try to anonymize the information? If so, how do I go about doing this?
Offline
#7 2024-11-25 20:11:22
- seth
- Member
- Registered: 2012-09-03
- Posts: 65,450
Re: Reducing network latency
No.
This will be LOCALHOST, _gateway, maybe some IPv4 - then your ISP and then the public nodes where the packages are routed.
The only thing you'll reveal is your ISP (they all suck) and roughly where you're located (country, maybe state - unless it's a very local ISP)
You can obfuscate that if you mind but if it's in the vicinity of the lag, you'll have to share that detail anyway.
Also please address the other questions.
Offline
#8 2025-01-03 21:31:17
- ThoughtBubble
- Member
- Registered: 2024-07-09
- Posts: 55
Re: Reducing network latency
Sorry for postponing this for so long.
Here are the pings and traceroutes for the Arch machine:
ping 8.8.8.8
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99162ms
rtt min/avg/max/mdev = 20.554/25.214/37.451/3.581 msping -4n google.com
--- google.com ping statistics ---
104 packets transmitted, 104 received, 0% packet loss, time 103165ms
rtt min/avg/max/mdev = 20.798/24.009/32.972/2.549 msping -n google.com
--- google.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99162ms
rtt min/avg/max/mdev = 20.385/25.063/56.410/4.923 msping archlinux.org
--- archlinux.org ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99139ms
rtt min/avg/max/mdev = 155.490/211.675/264.488/30.502 msping heise.de
--- heise.de ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99143ms
rtt min/avg/max/mdev = 124.239/182.285/234.255/30.279 mstracepath 8.8.8.8
1?: [LOCALHOST] pmtu 1500
1: _gateway 9.543ms
1: _gateway 7.712ms
2: syn-142-254-153-145.inf.spectrum.com 16.909ms
3: lag-61.hcr01clmboh55.netops.charter.com 19.477ms
4: lag-19.mcr11clmkohpe.netops.charter.com 17.228ms asymm 5
5: lag-31.rcr01clmkohpe.netops.charter.com 20.438ms
6: no reply
7: lag-11.chcgildt87w-bcr00.netops.charter.com 26.561ms
8: 74.125.48.174 36.374ms asymm 9
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500 tracepath google.com
1?: [LOCALHOST] pmtu 1500
1: _gateway 4.787ms
1: _gateway 4.785ms
2: syn-142-254-153-145.inf.spectrum.com 26.537ms
3: lag-61.hcr01clmboh55.netops.charter.com 23.437ms
4: lag-19.mcr11clmkohpe.netops.charter.com 17.272ms asymm 5
5: lag-27.rcr01clmkohpe.netops.charter.com 15.556ms
6: no reply
7: lag-11.chcgildt87w-bcr00.netops.charter.com 28.709ms
8: 72.14.212.162 28.396ms asymm 12
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500 tracepath archlinux.org
1?: [LOCALHOST] pmtu 1500
1: _gateway 4.204ms
1: _gateway 8.240ms
2: syn-142-254-153-145.inf.spectrum.com 24.499ms
3: lag-61.hcr01clmboh55.netops.charter.com 16.464ms
4: lag-19.mcr11clmkohpe.netops.charter.com 14.342ms asymm 5
5: lag-31.rcr01clmkohpe.netops.charter.com 15.546ms
6: no reply
7: ae13.edge2.chi10.sp.lumen.tech 38.218ms asymm 12
8: ae2.2.edge1.hel1.neo.colt.net 201.421ms asymm 16
9: 212.133.6.2 203.612ms asymm 15
10: core31.hel1.hetzner.com 206.772ms asymm 15
11: no reply
12: spine2.cloud1.hel1.hetzner.com 272.885ms asymm 16
13: no reply
14: 13229.your-cloud.host 273.204ms asymm 18
15: archlinux.org 203.002ms !H
Resume: pmtu 1500 tracepath heise.de
1?: [LOCALHOST] pmtu 1500
1: _gateway 4.098ms
1: _gateway 5.484ms
2: syn-142-254-153-145.inf.spectrum.com 16.369ms
3: lag-61.hcr01clmboh55.netops.charter.com 15.741ms
4: lag-19.mcr11clmkohpe.netops.charter.com 18.053ms asymm 5
5: lag-27.rcr01clmkohpe.netops.charter.com 17.940ms
6: lag-415-10.chctilwc00w-bcr00.netops.charter.com 28.484ms
7: ae13.edge2.chi10.sp.lumen.tech 30.302ms asymm 12
8: ae1.3110.edge4.frf1.neo.colt.net 234.640ms asymm 16
9: te2-2.c102.f.de.plusline.net 207.160ms asymm 18
10: 82.98.102.7 205.014ms asymm 18
11: no reply
12: no reply
13: 212.19.61.13 240.671ms !H
Resume: pmtu 1500===============================================================================================
===============================================================================================
===============================================================================================
===============================================================================================
===============================================================================================
===============================================================================================
Here are the results for the non-Arch machine:
ping 8.8.8.8
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 99 packets received, 1.0% packet loss
round-trip min/avg/max/stddev = 19.289/24.047/49.432/4.924 msping -n google.com
--- google.com ping statistics ---
100 packets transmitted, 97 packets received, 3.0% packet loss
round-trip min/avg/max/stddev = 19.343/24.265/36.928/3.177 msping archlinux.org
--- archlinux.org ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 148.074/152.451/175.545/4.194 msping heise.de
--- heise.de ping statistics ---
100 packets transmitted, 98 packets received, 2.0% packet loss
round-trip min/avg/max/stddev = 121.539/128.152/429.347/30.974 ms------------------------------------------------------------------------------------------------------------------------------------------------
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.530 ms 2.736 ms 2.818 ms
2 syn-142-254-153-145.inf.spectrum.com (142.254.153.145) 13.462 ms 58.440 ms 18.204 ms
3 lag-61.hcr01clmboh55.netops.charter.com (65.24.192.121) 13.943 ms 12.450 ms 12.494 ms
4 * lag-19.mcr11clmkohpe.netops.charter.com (65.29.17.148) 14.591 ms 17.165 ms
5 lag-31.rcr01clmkohpe.netops.charter.com (65.29.17.196) 14.432 ms 16.249 ms 12.927 ms
6 lag-25-10.chctilwc00w-bcr00.netops.charter.com (107.14.17.252) 23.887 ms *
lag-515-10.chctilwc00w-bcr00.netops.charter.com (71.74.44.32) 25.158 ms
7 lag-31.chcgildt87w-bcr00.netops.charter.com (66.109.10.82) 25.085 ms
lag-41.chcgildt87w-bcr00.netops.charter.com (66.109.0.228) 26.132 ms
lag-11.chcgildt87w-bcr00.netops.charter.com (66.109.6.20) 35.607 ms
8 syn-024-030-200-185.inf.spectrum.com (24.30.200.185) 27.700 ms
74.125.48.174 (74.125.48.174) 29.083 ms
192.178.69.202 (192.178.69.202) 25.624 ms
9 * * *
10 dns.google (8.8.8.8) 28.358 ms 27.283 ms 24.024 mstraceroute to google.com (142.250.191.206), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.484 ms 4.094 ms 2.739 ms
2 syn-142-254-153-145.inf.spectrum.com (142.254.153.145) 16.609 ms 13.531 ms 13.907 ms
3 lag-61.hcr01clmboh55.netops.charter.com (65.24.192.121) 15.256 ms 16.055 ms 12.276 ms
4 lag-19.mcr11clmkohpe.netops.charter.com (65.29.17.148) 35.547 ms 23.126 ms 13.962 ms
5 lag-27.rcr01clmkohpe.netops.charter.com (65.29.1.34) 16.130 ms
lag-31.rcr01clmkohpe.netops.charter.com (65.29.17.196) 16.303 ms
lag-27.rcr01clmkohpe.netops.charter.com (65.29.1.34) 20.037 ms
6 * * lag-415-10.chctilwc00w-bcr00.netops.charter.com (66.109.6.54) 28.108 ms
7 lag-31.chcgildt87w-bcr00.netops.charter.com (66.109.10.82) 24.003 ms
lag-41.chcgildt87w-bcr00.netops.charter.com (66.109.0.228) 24.314 ms
lag-11.chcgildt87w-bcr00.netops.charter.com (66.109.6.20) 25.104 ms
8 192.178.69.202 (192.178.69.202) 26.116 ms
72.14.212.162 (72.14.212.162) 28.246 ms
192.178.69.202 (192.178.69.202) 25.825 ms
9 * * *
10 ord38s31-in-f14.1e100.net (142.250.191.206) 29.221 ms 22.700 ms
142.251.60.4 (142.251.60.4) 26.759 mstraceroute to archlinux.org (95.217.163.246), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.151 ms 4.875 ms 4.729 ms
2 syn-142-254-153-145.inf.spectrum.com (142.254.153.145) 13.253 ms 22.404 ms 13.389 ms
3 lag-61.hcr01clmboh55.netops.charter.com (65.24.192.121) 13.567 ms 17.205 ms 16.320 ms
4 lag-19.mcr11clmkohpe.netops.charter.com (65.29.17.148) 13.975 ms 14.860 ms 13.803 ms
5 lag-27.rcr01clmkohpe.netops.charter.com (65.29.1.34) 15.355 ms
lag-31.rcr01clmkohpe.netops.charter.com (65.29.17.196) 13.091 ms
lag-27.rcr01clmkohpe.netops.charter.com (65.29.1.34) 13.718 ms
6 * lag-25-10.chctilwc00w-bcr00.netops.charter.com (107.14.17.252) 55.734 ms *
7 ae13.edge2.chi10.sp.lumen.tech (4.68.37.137) 26.687 ms 34.093 ms 28.715 ms
8 ae2.2.edge1.hel1.neo.colt.net (171.75.10.35) 145.302 ms 143.278 ms 144.651 ms
9 212.133.6.2 (212.133.6.2) 163.836 ms 150.761 ms 153.374 ms
10 core32.hel1.hetzner.com (213.239.224.26) 149.876 ms
core31.hel1.hetzner.com (213.239.224.38) 152.800 ms 152.994 ms
11 * * *
12 spine1.cloud1.hel1.hetzner.com (213.239.228.22) 179.882 ms
spine2.cloud1.hel1.hetzner.com (213.239.228.26) 156.795 ms
spine2.cloud1.hel1.hetzner.com (213.239.228.50) 154.212 ms
13 * * *
14 13229.your-cloud.host (95.216.131.48) 168.926 ms 152.598 ms 152.493 ms
15 archlinux.org (95.217.163.246) 149.742 ms !X 153.992 ms !X 154.355 ms !Xtraceroute to heise.de (193.99.144.80), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 5.624 ms 2.878 ms 7.083 ms
2 syn-142-254-153-145.inf.spectrum.com (142.254.153.145) 16.211 ms 17.029 ms 16.210 ms
3 lag-61.hcr01clmboh55.netops.charter.com (65.24.192.121) 133.982 ms 15.059 ms 134.725 ms
4 lag-19.mcr11clmkohpe.netops.charter.com (65.29.17.148) 24.340 ms 19.893 ms 17.207 ms
5 lag-31.rcr01clmkohpe.netops.charter.com (65.29.17.196) 133.684 ms 16.183 ms
lag-27.rcr01clmkohpe.netops.charter.com (65.29.1.34) 136.578 ms
6 * * lag-515-10.chctilwc00w-bcr00.netops.charter.com (71.74.44.32) 25.440 ms
7 * ae13.edge2.chi10.sp.lumen.tech (4.68.37.137) 27.822 ms 32.220 ms
8 ae1.3110.edge4.frf1.neo.colt.net (171.75.8.85) 121.625 ms 119.318 ms 123.191 ms
9 te2-2.c102.f.de.plusline.net (212.162.24.58) 126.957 ms 126.010 ms 124.415 ms
10 82.98.102.7 (82.98.102.7) 124.053 ms
82.98.102.71 (82.98.102.71) 121.429 ms 121.207 ms
11 * * *
12 * * 212.19.61.13 (212.19.61.13) 126.816 ms !X
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * 212.19.61.13 (212.19.61.13) 137.098 ms !X *
19 * * *
20 * * *
21 212.19.61.13 (212.19.61.13) 126.117 ms !X * *
22 * * *
23 * * *
24 * * *
25 * * *
26 212.19.61.13 (212.19.61.13) 125.373 ms !X * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * 212.19.61.13 (212.19.61.13) 129.922 ms !X *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * 212.19.61.13 (212.19.61.13) 125.702 ms !X
51 * * *
52 * * *
53 * * *
54 212.19.61.13 (212.19.61.13) 128.565 ms !X * *
55 * * *
56 * 212.19.61.13 (212.19.61.13) 124.934 ms !X *
57 * * *
58 * * *
59 * * *
60 212.19.61.13 (212.19.61.13) 128.626 ms !X * *
61 * * *
62 * * *
63 * 212.19.61.13 (212.19.61.13) 131.046 ms !X *
64 * * *Last edited by ThoughtBubble (2025-01-04 05:14:06)
Offline
#9 2025-01-03 22:51:02
- seth
- Member
- Registered: 2012-09-03
- Posts: 65,450
Re: Reducing network latency
Please use [code][/code] tags. Edit your post in this regard.
It's likely your DNS, see how the IP and -n pings are comparable among systems and vastly outperform the ones w/ the reverse domain lookup?
If you don't have a DNS cache in your LAN (dnsmasq in your router or so) use a local one (resolved, dnsmasq on your system, stubby), https://wiki.archlinux.org/title/Domain … NS_servers - any caching stub resolver will do.
Or consider configuring a better DNS (I assume right now you're using your ISPs one?)
Offline
Pages: 1