We currently queue up to 64 requests, and fire them all at once. Making 64 requests at once can overwhelm some routers. <rdar://problem/8105498>
Created attachment 59150 [details] proposed fix
Comment on attachment 59150 [details] proposed fix Using a HashSet means the order of the names is based on hash table ordering, essentially random. Should we do something to preserve the order?
Comment on attachment 59150 [details] proposed fix r=me How did you test that this scheme does not overwhelm important gateways?
Since you are fixing the comment on line 58 of WebCore/platform/network/cf/DNSCFNet.cpp, maybe you can fix a spelling error as well "appications'".
I am not aware of a strong reason why ordering would be important (my comment in code about dropping newer names notwithstanding). > How did you test that this scheme does not overwhelm important gateways? We know that chromium uses 8 parallel requests (because it has 8 loader threads), so I'm relying on matching them. Also, a co-worker seems to be able to reproduce the problem, so we'll test to see if a nightly resolves it.
Committed <http://trac.webkit.org/changeset/61435>.