Lines Matching full:resolutions
469 Duration of time spent by ProcTask in failing fallback resolutions.
475 Duration of time spent by ProcTask in successful fallback resolutions.
635 Duration of time taken by DnsTask in resolutions that failed. Excludes time
644 synchronous resolutions (as IP literals, from cache, and from HOSTS).
650 Duration of time taken by DnsTask in resolutions that succeeded.
724 resolutions using DnsTask.
731 resolutions using DnsTask.
2272 Duration of time taken in OS resolutions for actual navigations. These
2274 was already completed by an earlier attempt. Note that cached resolutions
2302 Duration of time taken in OS resolutions that succeeded and were requested
2305 attempt. Note that cached resolutions may provide low (0ms?) resolution
2497 name via the network. Any resolutions that are faster than 15ms are
2501 network-based resolutions induced by this feature. Not all these
2502 resolutions prove helpful (i.e., the user does not always actually visit the
2573 name via the network. Any resolutions that are faster than 15ms are
2577 network-based resolutions induced by this feature. Not all these
2578 resolutions prove helpful (i.e., the user does not always actually visit the
2603 Counts of successes and failures of OS resolutions in various categories.
2609 Duration of time taken in OS resolutions for actual navigations. Note that
2610 cached OS resolutions may provide low (0ms?) resolution times.
2628 Duration of time taken in speculative OS resolutions. Note that cached OS
2629 resolutions may provide low (0ms?) resolution times.
2636 that cached resolutions may provide low (0ms?) resolution times.
2642 Duration of time taken in OS resolutions that succeeded and were requested
2643 for actual navigations. Note that cached resolutions may provide low (0ms?)
2699 currently anticipated. Such resolutions are termed "Unexpected
2700 Resolutions," and the durations associated with those DNS resolutions
2703 resolutions should be done when a primary resolution (or navigation) takes
2718 anticipated (since scanning in not allowed by default). Such resolutions are
2719 termed "Unexpected Resolutions," and the durations associated with
2720 those navigation induced DNS resolutions are shown below. If a referring
30824 <int value="1" label="Resolutions Differ"/>
30825 <int value="2" label="Resolutions Agree"/>
31470 resolutions in this test"/>
31498 label="with only 4 concurrent speculative resolutions done in parallel"/>
31522 label="with only 10 concurrent resolutions done in parallel"/>
31524 label="with only 14 concurrent resolutions done in parallel"/>
31526 label="with only 20 concurrent resolutions done in parallel"/>
31528 label="with only 6 concurrent resolutions done in parallel"/>
31530 label="with only 7 concurrent resolutions done in parallel"/>
31532 label="with only 8 concurrent resolutions done in parallel"/>
31534 label="with only 9 concurrent resolutions done in parallel"/>
31536 label="with the default number of concurrent resolutions done in
