LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   Sooo slow Firefox on Suse 11.2 (https://www.linuxquestions.org/questions/suse-opensuse-60/sooo-slow-firefox-on-suse-11-2-a-769848/)

simjii 11-18-2009 12:08 AM

Sooo slow Firefox on Suse 11.2
 
Just installed Suse 11.2 on a computer which was running on Suse 10.3.
After switching to 11.2 I realized that web page loading speed on Firefox is so slow. On the same network my 7 years old laptop can load the same page much faster and even my android smartphone. To load a web page first time it takes about 10 seconds on Suse 11.2 with firefox.
It is not just a specific web site problem.
Did anybody notice this problem or just me?
Is there any way to make Firefox faster. I even updated Firefox to 3.5.5 but no difference.

System info.
Suse 11.2 with KDE, wired network with dynamic IP.

Any help is appreciated.

salasi 11-18-2009 03:35 AM

Do you have both ipv4 and ipv6 enabled?

simjii 11-18-2009 08:24 PM

Yes both were enabled.
I just disabled ipv6 but it dose not seem helping.
Should I disable ipv4 instead ipv6?

simjii 11-18-2009 10:58 PM

I think problem is solved.
It is caused by Firefox configuration. A simple solution is disabling ipv6 support in Firefox.
It has nothing to do with ipv6 in network setting.
The same problem was already reported on early version of Suse but i didn't have this problem with 10.3.
Here is how to disable ipv6 in Firefox. Taken from the thread linked below.

enter in FF address bar:
about:config
(no spaces above)
in the search bar inter ipv6
change the vaule of
network.dns.disableIPv6
from false to true

http://www.linuxquestions.org/questi...-wrong-408058/

Cogar 11-28-2009 02:13 PM

Thank you for posting the solution, simjii. It made a huge difference for me. :hattip:

terryxela 11-28-2009 02:17 PM

Quote:

Originally Posted by simjii (Post 3762187)
I think problem is solved.
It is caused by Firefox configuration. A simple solution is disabling ipv6 support in Firefox.
[/url]

The problem may be a little more complex than your approach and may show in other way like in the software manager, wget, etc.
Look at

https://bugzilla.novell.com/show_bug.cgi?id=547658

A quick test would be to enable ipv6 under firefox and add the DNS servers either from you isp or public dns
208.67.222.222
208.67.220.220
and then run firefox and see if it fix it.

If that is the case they are working on to fix it.

-=terry=-

simjii 11-28-2009 04:29 PM

terryxela

You are right. I just did quick test to reproduce the bug.
As reported in the bug linked in your post I can speed up firefox by adding
"options single-request" in /etc/resolv.conf.
I also realized that SUSE 11.0 doesn't seem to have this problem.
There is no difference in network setting and Firefox ipv6 setting between 11.0 and 11.2 on my computers but Firefox is so slow to look up pages only on 11.2.
Disabling ipv6 on Firefox is only a temporary work around.

terryxela 11-29-2009 08:49 AM

The best work around would be

1. enable ipv6 in firefox

2. remove the extra line in resolv.conf.

so you are back to the beginning ;-)

3. find out the dns servers from your isp. In my case I just enter the ip address of the router http://192.168.0.1 on firefox. This open the router and I can get the 2 dns from there.

4. open yast/network devices/network setting
/global options and enable traditional method with ifup then
/hostname/DNS an enter the ip of the 2 DNS from your isp under Name Server 1 and Name Server 2.
Of course you can enter instead the public DNS but I do not think is right, I just keep the public DNS in case the isp DNS has a problem. Of course you can added as a Name Server 3 and it will not be utilize except if the other 2 fail

Now you should be OK. This procedure make your system as if would not have the bug. Everything should work well. The only downside is that the knetmanager is not enable but if it is a workstation you do not need it any way. It is is a laptop you have to do another step before connecting.

-=terry=-

Note: the cause of the bug is in Petr message #12 of

https://bugzilla.novell.com/show_bug.cgi?id=549447


All times are GMT -5. The time now is 12:01 PM.