Bug 19396
| 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 | ||
Vance Dubberly
When using the network timeline in web inspector to check load times I notices that requests that show up in Firefoxes time line as taking 3-5ms show up in Webkits inspector as taking 180-225ms. I double check this against ab and Firefox is accurate. I've checked this against a number of sites... for instance yahoo( 69ms vs 282ms ) and google (10ms vs 367 ms).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Roben (:aroben)
Maybe we're not measuring the same thing?
What's "ab"?
Vance Dubberly
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....
Timothy Hatcher
Has this changed now that we show latency separately?
Alexander Pavlov (apavlov)
The times reported in the bug congrue with currently-rendered "download" vs "total" times, closing.
Alexander Pavlov (apavlov)
Fix resolution status as advised by AP