jayk1961 / arora

Automatically exported from code.google.com/p/arora
0 stars 0 forks source link

Slow on Comcast DNS #660

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Arora browser slow on Fedora11 with Comcast DNS servers.  This might be due to 
ipv6 requests, 
comast's DNS servers are horrible for that.  Problem clears when switching to 
opendns.  

What steps will reproduce the problem?
1. allow comcast's default dns servers to remain (74.125.127.100 is one of them)
2. attempt to connect to ay website.
3. wait until it loads (google took me 10-30 seconds) 

What is the expected output? What do you see instead?
Expect comperable speed to firefox or konq

What version of the product are you using? On what operating system?
tried on both 0.90 from Fedora 11 repos and with git head commit 
138994e74d1637c4d3efbaa98538ff0b5daa05bb (Fri Sep 25 23:09:25 2009 +0300)
both on Fedora 11 64bit

Original issue reported on code.google.com by unama...@gmail.com on 27 Sep 2009 at 4:12

GoogleCodeExporter commented 9 years ago
oops comcast dns should read 68.87.74.166

Original comment by unama...@gmail.com on 27 Sep 2009 at 5:02

GoogleCodeExporter commented 9 years ago
Do you happen to have a linksys router?

What does the following command eventually print out?
dig doestnexist.kde.org aaaa @68.87.74.166

Original comment by ice...@gmail.com on 28 Sep 2009 at 6:52

GoogleCodeExporter commented 9 years ago
Some further metrics: 
- With Comcast's DNS xkcd took 32 seconds to load with comcast's DNS in arora 
and under 2 seconds in konq
- WIth OpenDNS both were under 2.

To answer your questions:

I do have a lynksys router (a WRT110)

The dig command did not very take long:

[unamanic@gimli ~]$ dig doestnexist.kde.org aaaa @68.87.74.166

; <<>> DiG 9.6.1-P1-RedHat-9.6.1-6.P1.fc11 <<>> doestnexist.kde.org aaaa 
@68.87.74.166
;; global options: +cmd                                                         

;; Got answer:                                                                  

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13522                      

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0            

;; QUESTION SECTION:
;doestnexist.kde.org.           IN      AAAA

;; AUTHORITY SECTION:
kde.org.                900     IN      SOA     ns1.kde.org. sysadmin.kde.org. 
2009092301 10800 3600 2419200 
86400

;; Query time: 78 msec
;; SERVER: 68.87.74.166#53(68.87.74.166)
;; WHEN: Mon Sep 28 16:57:27 2009       
;; MSG SIZE  rcvd: 86                   

Original comment by unama...@gmail.com on 28 Sep 2009 at 9:15

GoogleCodeExporter commented 9 years ago
Could you edit  src/browserapplication.cpp and look for the line where
QWebSettings::DnsPrefetchEnabled is set and set it to false and try again?
Does it change anything?

Original comment by Markus.G...@gmail.com on 1 Oct 2009 at 12:45

GoogleCodeExporter commented 9 years ago
It did not help, however I did not expect that it would because I'm using: 
qt-devel-4.5.2-3.fc11.x86_64

Original comment by unama...@gmail.com on 1 Oct 2009 at 9:37

GoogleCodeExporter commented 9 years ago
This is issue does not happen on Fedora rawhide.

Original comment by unama...@gmail.com on 12 Oct 2009 at 4:42