Comment #23 on issue 12754 by [email protected]: "Resolving host" takes forever; disabling prefetching helps http://code.google.com/p/chromium/issues/detail?id=12754
There are imaginable ways that DNS latency may be key, or it may be that some tangential related problem is causing the delay. We have (in the past) seen cases where unusual setups (example: a 5MB etc/hosts file that was being scanned often) that induced problems, and we tried to put in back-off measures that cause DNS prefetching to detect latency, and diminish its activity. The first thing to do is look at actual numbers, and try to see if it is measurable DNS latency, and the about:histograms/DNS should provide a lot of objective data. If you are seeing this overall delay consistently, please attach a snapshot of that internal page, and it will help us direct our efforts. Having seen "remarkable configurations," it is very believable that disabling prefetching in those cases may help. Given that it does not significantly help in some cases, I'm sure there are several issues involved. It might be interesting to (on the same machine) run two instances of chrome, one with, and one without prefetching enabled (you'll need two separate profiles). This could hint to us as to whether the OS, or LAN connection is starting to slow, or if the instance of chrome is getting lethargic. Keep in mind that IF you're visiting the sames sites in the two instances, then the OS will tend to cache DNS records, and the "second browser" to navigate will get a lot of benefit (even if it has DNS prefetching disabled). Thanks in advance for providing some specific info. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
