Apparently the add/conversion/etc scripts that are embedded at various points throughout the doh website have been causing some tremendous slowdowns. Took hours and hours to track that down today.

Also firefox really seems to hate amazon's S3 content delivery service. Chrome, Safari (even IE) seem to resolve nice and quickly, but the fox hates it. Since all of our images/css/js comes from Amazon, that is why firefox is running slow. We've been tuning that today, and now at least mine loads up, but it still isn't snappy...

Do you know if this is a Firefox 3.x issue, or inherent in all versions of firefox? I still haven't been able to determine if anybody's compared Chrome to Flock yet, which is based on FF 2.x, and which is why it's always handled DoH better than FF.

If Chrome's really the most functional, I'll re-install it, under sufferance, but I won't like it. :shakehead:

I can confirm that when I tested Flock vs Chrome, chrome outrun Flock by a mile. I took about 35-40mins equipping a charm bag with FF compared to about 5-10min with Chrome.


P.S. Freezing issue still there for FF on my laptop. Seems its fixed for others though. Could just be me. Well, I'm going chrome anyway.

Another thing to research - ipv6 with Firefox. I've heard that having ipv6 enabled (which it might be by default now) can cause the DNS resolution to take a long time. If anyone gets info on that, I'd love to hear it.

"One particular bug that has appeared exists not in Mozilla, but in IPv6-capable DNS servers: an IPv4 address may be returned when an IPv6 address is requested. It is possible for Mozilla to recover from this misinformation, but a significant delay is introduced."

"Network.dns.disableIPv6". mozillaZine. 17 February 2010. http://kb.mozillazine.org/Network.dns.disableIPv6


IPv6

Firefox supports IPv6 by default, which may cause connection problems on certain systems. To disable IPv6 in Firefox:

In the Location bar, type about:config and press EnterReturn.

The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.

In the Filter field, type network.dns.disableIPv6.

In the list of preferences, double-click network.dns.disableIPv6 to set its value to true.

http://support.mozilla.com/en-US/kb/Fir ... s+can#IPv6


"If the browser is used in commercial environment, then you have to ask your company's network administrator."

"This will disable IPv6. Most of DNS servers are still IPv4, so it will speedup Web browsing with Firefox."

http://wiki.opensuse.org/SDB:Disable_IPv6_for_Firefox

Awesome Koma - thanks :mrgreen:

Can anyone confirm that this has sped up Firefox for them? I set mine up, and it did help quite a bit. Still not nearly as fast as Chrome, but much better than before.

There must be something that is cycling in the code.

I am on 64bit kubuntu linux, running 3.6.3.

The reason I say there must be something that is cycling, is due to the fact I can watch all my connections, cpu and ram usage. In trying to load domain of heroes login page one core (got a quad) goes to 100% usage and the memory steadily increases a by about .1GB per interval on a simple nice slope.

Once it passes 4G of ram, my system pretty much dies.

The s3.amazonaws.com is active and usually at least 1 of the 1e100.net (google safebrowsing links) are showing along with the DoH main connect.

Not sure if this will be helpful in tracking down the problem.

My Firefox just gives the Not Responding message of Doom either way.

Did one more test just now, and got to the choose character screen.

Once I selected my first character, had the CPU spike, 2 amazon numeric IP links and a steady increase of ram till about 3.7G when I killed it.

The first 2 screens to get to the character select ran up a lot of ram then dropped it once the page was completed.

Might want to check the amazon oddness.

By actively blocking amazon I was able to get through the first 2 screens, but once a character is selected, the ram usage keeps shooting up and up till the system dies on FF.

Basically it always seems to happen when media-domainofheroes is called, where it starts.