Comment #35 on issue 12754 by j...@chromium.org: "Resolving host" takes forever; disabling prefetching helps http://code.google.com/p/chromium/issues/detail?id=12754
@ben.rowland: I don't have an answer for you yet... but I'll try to ramble on a bit about what is happening, and what these pages mean. I'll also ask a question or two, and suggest you possibly try google's public dns service. The about:dns page suggests that it is only www.google.com and www.google.co.uk that are being visited. My guess it that you have the latter as your home page, and it pulled some resources from www.google.com, but that is all you had done so far in this session. I'm guessing you sent this set of files because it was THIS session that produced the bothersome pause. The second file provided details for all the pre-resolutions performed so far in this session. It indicates that a total of 13 names had been pre-resolved (probably 10 from a startup list, and 3 from scanning the startup page(s)). Apparently 8 of the resolutions took under 118ms (4 in about 40 ms, 2 in about 55ms, 1 in 75ms and 1 in about 100 ms), but there were 5 that took between 4.5 and 6 seconds! 5 seconds is a very big number, and might mean that after resolving 8 names in rapid succession, that your resolver suddenly decided to take its sweet time. The pre-resolution start-up code maintains a list of no more than 10 domains to load at startup. Chromium also avoids pre-resolving more than 8 names at any one time (holding other pre-resolutions in a queue as needed). Based on the DNS.PreftchQueue time, I can see that nothing sat very long in the prefetch-queue (max was about 190 ms.) The fact that 18 entries had queuing delay time, but there were only 13 resolution timings just meant that duplicates (in a very small time frame) were discarded, or that some resolutions took under 15 ms (and were considered cache hits, not worth timing). Linux doesn't generally have any DNS cache at the OS level, and so it was probably your firewall that was providing an intermediate resolver, although it might be that you were directed to your ISP's resolver. You might run "nslookup" from a command prompt, and see if the resolver in use is on your lan, or it is at a routable address perchance at an ISP. If it is at your ISP, I'd be very curious to see if Google's recent public DNS service http://code.google.com/speed/public-dns/ could help you. If the problem appears at a resolver in your firewall (on your lan), it would be nice if you posted the name/version/etc. for your router/firewall, so we can see if there is any pattern detected about folks experiencing this problem. -- 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
