RESOLVED WORKSFORME 19396
Network Timeline Shows very wrong milliseconds 
https://bugs.webkit.org/show_bug.cgi?id=19396
Summary Network Timeline Shows very wrong milliseconds
Vance Dubberly
Reported 2008-06-04 14:03:31 PDT
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)
Comment 1 2008-06-05 03:39:01 PDT
Maybe we're not measuring the same thing? What's "ab"?
Vance Dubberly
Comment 2 2008-06-05 21:06:46 PDT
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
Comment 3 2008-08-19 11:46:59 PDT
Has this changed now that we show latency separately?
Alexander Pavlov (apavlov)
Comment 4 2010-03-12 07:27:01 PST
The times reported in the bug congrue with currently-rendered "download" vs "total" times, closing.
Alexander Pavlov (apavlov)
Comment 5 2010-03-18 03:54:40 PDT
Fix resolution status as advised by AP
Note You need to log in before you can comment on or make changes to this bug.