Freshly installed EOS after 6 months. When I make a search query/press enter on a weblink, it takes probably 35 seconds or maybe 20 seconds at least before anything loads.
Speedtest gives satisfactory results. No issues there.
It is the initial delay that is irritating me. Do not know what it is called in technical terms. Will be happy to give any terminal output you need.
Performance is a variable thing. I know if I install KDE Plasma on one of my old weak spec’d Intel NUCs, it’s going to be painfully, painfully slow. LXQt on the other hand, plain as it is, runs great on that old modest hardware.
You might like to provide some details of your setup, so we can have at least an idea of what you might be able to expect. Could you share the link this produces please?
inxi -Fxxc0z | eos-sendlog
Thank you for the response.
Here is the output:
https://0x0.st/XRPl.txt
I appreciate you providing that. I think it’s fair to say your hardware shouldn’t be an issue, so we can rule that out as a basic premise.
Might you try some tests?
time ping 1.1.1.1 -c 1
time ping cloudflare.com -c 1
time nslookup quad9.net
Latency is the thing I’m trying to test for with these.
ime ping 1.1.1.1 -c 1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=48.2 ms
--- 1.1.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 48.243/48.243/48.243/0.000 ms
real 0m0.059s
user 0m0.007s
time ping cloudflare.com -c 1
PING cloudflare.com (104.16.133.229) 56(84) bytes of data.
64 bytes from 104.16.133.229: icmp_seq=1 ttl=58 time=3.77 ms
— cloudflare.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.769/3.769/3.769/0.000 ms
real 0m10.137s
user 0m0.005s
sys 0m0.005s
time nslookup quad9.net
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
Server: 202.88.131.91
Address: 202.88.131.91#53
Non-authoritative answer:
Name: quad9.net
Address: 216.21.3.77
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
Name: quad9.net
Address: 2620:0:871:9000::77
real 0m30.182s
user 0m0.014s
sys 0m0.019s
[sri@LinuxBoy ~]$ time nslookup quad9.net
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
Server: 202.88.131.91
Address: 202.88.131.91#53
Non-authoritative answer:
Name: QUAD9.net
Address: 216.21.3.77
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
;; communications error to 202.88.149.6#53: timed out
Name: QUAD9.net
Address: 2620:0:871:9000::77
real 0m30.137s
user 0m0.010s
sys 0m0.013s
In my experience:
it is agnostic of search engine. It seems to be stuck for longer than usual initially, and it keeps going once out of that.
Have not tried a different browser. I can this persists though.
Upon entering web-address the load time is similar, but better than just typing something in address bar and waiting to load.
The results there:
The apparent issue isn’t your connection, it’s DNS resolution. The first ping test which was completed in a fraction of a second, bypassed DNS lookup. The other two, engage DNS lookups.
Is your router assigning your DNS? Are you able to change your DNS server?
I would recommend considering Quad9 for that, as a privacy respecting option.
Thank you so much for the diagnosis! From the little knowledge I have, this seems pretty much the case . Will switch DNS and take a look at Quad9 for sure!!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.