Hi AndyH28,
I experienced the same problems like you: High latency spikes, when I am on Wifi. As I work quite a time via SSH on remote machines, a constant latency is crucial. Otherwise typing is horrible.
I googled around and found the same answers like you got:
- This 5GHz thing
- Distance to router
- Hardware issues
However I couldn't believe those answers and none of them applied to my problem. The only thin that worked was using a wired connection.
During the last weeks I spend many hours investigating the problem. My start always was a "ping session" like this:
64 bytes from 216.58.205.227: icmp_seq=53 ttl=56 time=32.462 ms
64 bytes from 216.58.205.227: icmp_seq=54 ttl=56 time=98.429 ms
64 bytes from 216.58.205.227: icmp_seq=55 ttl=56 time=149.815 ms
64 bytes from 216.58.205.227: icmp_seq=56 ttl=56 time=32.795 ms
64 bytes from 216.58.205.227: icmp_seq=57 ttl=56 time=12.920 ms
64 bytes from 216.58.205.227: icmp_seq=58 ttl=56 time=12.892 ms
64 bytes from 216.58.205.227: icmp_seq=59 ttl=56 time=12.899 ms
64 bytes from 216.58.205.227: icmp_seq=60 ttl=56 time=12.902 ms
64 bytes from 216.58.205.227: icmp_seq=61 ttl=56 time=12.851 ms
64 bytes from 216.58.205.227: icmp_seq=62 ttl=56 time=223.226 ms
64 bytes from 216.58.205.227: icmp_seq=63 ttl=56 time=148.654 ms
64 bytes from 216.58.205.227: icmp_seq=64 ttl=56 time=206.037 ms
64 bytes from 216.58.205.227: icmp_seq=65 ttl=56 time=268.655 ms
64 bytes from 216.58.205.227: icmp_seq=66 ttl=56 time=17.800 ms
64 bytes from 216.58.205.227: icmp_seq=67 ttl=56 time=47.629 ms
64 bytes from 216.58.205.227: icmp_seq=68 ttl=56 time=143.621 ms
64 bytes from 216.58.205.227: icmp_seq=69 ttl=56 time=29.277 ms
64 bytes from 216.58.205.227: icmp_seq=70 ttl=56 time=88.440 ms
64 bytes from 216.58.205.227: icmp_seq=71 ttl=56 time=139.968 ms
64 bytes from 216.58.205.227: icmp_seq=72 ttl=56 time=12.865 ms
64 bytes from 216.58.205.227: icmp_seq=73 ttl=56 time=12.303 ms
64 bytes from 216.58.205.227: icmp_seq=74 ttl=56 time=12.941 ms
64 bytes from 216.58.205.227: icmp_seq=75 ttl=56 time=12.903 ms
64 bytes from 216.58.205.227: icmp_seq=76 ttl=56 time=12.924 ms
64 bytes from 216.58.205.227: icmp_seq=77 ttl=56 time=182.978 ms
64 bytes from 216.58.205.227: icmp_seq=78 ttl=56 time=104.746 ms
64 bytes from 216.58.205.227: icmp_seq=79 ttl=56 time=154.806 ms
64 bytes from 216.58.205.227: icmp_seq=80 ttl=56 time=217.942 ms
64 bytes from 216.58.205.227: icmp_seq=81 ttl=56 time=275.957 ms
64 bytes from 216.58.205.227: icmp_seq=82 ttl=56 time=12.061 ms
64 bytes from 216.58.205.227: icmp_seq=83 ttl=56 time=95.393 ms
64 bytes from 216.58.205.227: icmp_seq=84 ttl=56 time=140.254 ms
64 bytes from 216.58.205.227: icmp_seq=85 ttl=56 time=25.608 ms
64 bytes from 216.58.205.227: icmp_seq=86 ttl=56 time=81.580 ms
64 bytes from 216.58.205.227: icmp_seq=87 ttl=56 time=12.871 ms
64 bytes from 216.58.205.227: icmp_seq=88 ttl=56 time=12.501 ms
64 bytes from 216.58.205.227: icmp_seq=89 ttl=56 time=13.127 ms
64 bytes from 216.58.205.227: icmp_seq=90 ttl=56 time=12.874 ms
64 bytes from 216.58.205.227: icmp_seq=91 ttl=56 time=12.908 ms
As you might see, there is some pattern (highlighted in both).
After capturing network traffic with Wireshark, and opening/closing the programs I normally used, I identified multiple programs which, when running, trigger this behaviour. Meaning: Once I run the particular program the latency pattern shows and after closing, the latency is gone.
Unfortunately, two of these programs are constantly running on my machine, because I use them a lot:
Now that I knew the trouble causing programs, I scanned their preferences for mysterious settings. Both tools require a network connections for some feature:
- The database tool searches for "remote options" (whatever that is)
- The TEX tool queries a grammar checker
After disabling this options, the programs can run and don not interfere with the network connection. And I my case, I didn't need the features I disabled.
So, I don't know if this is the ultimate solution, but I'm happy right now. Maybe there is something else, because like I said: there are no issues (independent from program options), when the MAC is connected via ethernet. It is a Wifi only issue.
Hope I could help
JR