Your browser is instrumented to reveal some data that would be helpful in understanding this performance. Since you're seeing times greater than 60 seconds, something big should show up. If possible, please visit (in chromium):
about:histograms/DNS You'll see a pile of ASCII art histograms, which reflect what has been going on with regard to DNS fetching. None of the information should be very confidential, so if possible, please cut/paste/post a copy here for folks to look at. It may, for example, be that the DNS resolver in Vmware is restricting the the rate of resolutions, rather than allowing them to happen in parallel. Without taxing most computers or networks, Chromium currently tries to do up ot 8 resolutions in parallel. If this were a problem, then you'd see a large average queueing delay (as resolutions backed up into the queue) in the histogram labeled DNS. PrefetchQueue. The median for that histogram should be tiny (around 1ms), but the mean could be much larger if you visit pages with a LOT of domains (wikipedia comes to mind). Even so, I'd be rather surprised to hear about queuing delay over 1 second. As a second example, for some reason your DNS resolution time may be terrible. If so, you'd see this in the histogram labeled DNS.PrefetchFoundNameL (where I'd commonly expect to see a median value around 85ms, and mean value up closer to 200-600ms). If you see a long tail (resolutions larger than a second or two, meaning larger than 1000-2000ms along the axis on the left), then there may be a problem with your resolver or your network. I've seen especially long tails in negative results (host not found) on networks when netbios kicks in and does various work to broadcast in order to find local hosts. Again, please post a copy of your DNS histograms after you encounter this problem. Thanks, Jim On Feb 9, 8:06 pm, Bob Doe <[email protected]> wrote: > I'm running Chrome under Vmware Fusion 2.0. If I have "Use DNS pre- > fetching to improve page load performance" turned on, many websites I > visit seem to stall for a long time (> 60 seconds) at "Resolving > host..." before web pages are rendered. I have found other people on > the web complain about the same problem, what is the underlying cause, > and is there plan to fix this problem in upcoming releases? --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
