Summary: | Network Timeline Shows very wrong milliseconds | ||
---|---|---|---|
Product: | WebKit | Reporter: | Vance Dubberly <altjeringa> |
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | apavlov, aroben, rik, timothy |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All |
Description
Vance Dubberly
2008-06-04 14:03:31 PDT
Maybe we're not measuring the same thing? What's "ab"? While ya'll make in fact be measuring the metric differently, the timeline appears to mean "it took (n) milliseconds to load (x) resource". I think most people will believe that means "request initiated thru server finishes transmit." Which is what mozilla ab, httperf etc measure. ab = Apache Benchmark... <APACHE_ROOT>/bin/ab thanks.... Has this changed now that we show latency separately? The times reported in the bug congrue with currently-rendered "download" vs "total" times, closing. Fix resolution status as advised by AP |