Updates:
Labels: -Mstone-4 Mstone-X
Comment #18 on issue 9598 by j...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
It appears that we are not actually working on this. Moving to mstone-x.
--
You received this message because yo
Comment #13 on issue 9598 by petr.gurecky: We need to throttle DNS request
http://code.google.com/p/chromium/issues/detail?id=9598
Hi, my problem seems to be related to the stuff you're discussing here
about(?):
When loading some site it takes approx. 3-5 secs when saying
only 'Resolving hos
Comment #12 on issue 9598 by ero...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
> It looks like mozilla bounds number of connections to 24:
For comparison, neither IE7 nor Safari4 are bounding the total number of
sockets.
(Looks like
Comment #11 on issue 9598 by w...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
Why don't we use a histogram to find out the number of simultaneous
connections that our users are actually using, and then base the
total socket limit on tha
Comment #8 on issue 9598 by omattos: We need to throttle DNS request
http://code.google.com/p/chromium/issues/detail?id=9598
We need to make sure that "timeout" occurs quickly. The way you suggest
means if one
UDP DNS request packet goes missing, the user may be waiting 30-60 secs for
the p
Updates:
Status: Available
Labels: Mstone-2.1
Comment #6 on issue 9598 by j...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
(No comment was entered for this change.)
--
You received this message because you are listed in
Comment #5 on issue 9598 by ero...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
> Could we check that we limit the number of connections to a single
> host (including resolution) early enough in the process that we
> preclude such a scen
Updates:
Cc: -p...@chromium.org
Comment #4 on issue 9598 by j...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
Per huanr's comment.. focusing only on "being good citizens,"...
It is easy to envision a page that requires 100 or mo
Comment #3 on issue 9598 by hu...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
The crash itself is tracked at 8544. The purpose of this bug is to discuss
whether we
need to be a good citizen of the system by setting our dns query limit
Updates:
Cc: p...@chromium.org
Comment #2 on issue 9598 by j...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
Eroman's analysis appears to be spot on.
The prefetcher is supposed to limit its activity to 8 outstanding requsets,
Updates:
Cc: j...@chromium.org
Comment #1 on issue 9598 by ero...@chromium.org: We need to throttle DNS
request
http://code.google.com/p/chromium/issues/detail?id=9598
Is this actually causing problems?
The DNS resolving is using a windows thread pool, which defaults to a
maximum of
Status: Untriaged
Owner:
CC: da...@chromium.org, w...@chromium.org, ero...@chromium.org
Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend Size-Medium
New issue 9598 by hu...@chromium.org: We need to throttle DNS request
http://code.google.com/p/chromium/issues/detail?id=9598
I was looking
12 matches
Mail list logo