Comment #15 on issue 14478 by [email protected]: Add profiling data
for recent network requests
http://code.google.com/p/chromium/issues/detail?id=14478
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=25425
------------------------------------------------------------------------
r25425 | [email protected] | 2009-09-03 19:36:16 -0700 (Thu, 03 Sep 2009)
| 7 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/load_log_event_type_list.h?r1=25425&r2=25424
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/url_request/url_request.cc?r1=25425&r2=25424
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/url_request/url_request_unittest.cc?r1=25425&r2=25424
Add trace-point for URLRequest to the LoadLog.
This is probably the most important metric, since it measures the initial
latency of the request (until when we get the headers back).
BUG=http://crbug.com/14478
Review URL: http://codereview.chromium.org/194018
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
