Use start timing recorded in the renderer for fetchStart
Currently, a fetch event for navigation can be dispatched without waiting for an ACK message of StartWorker. That resulted in recording the time for PerformanceResourceTiming#fetchStart and requestStart before the worker becomes ready to get a fetch event. This CL changes the time used for them. Before this CL, these time were recorded when the worker becomes ready and just before sending a message to fire a FetchEvent. After this CL, fetchStart and requestStart uses the time when the fetch event is actually dispatched on the worker thread. As a result, we can measure the time spent for starting the worker thread by fetchStart - workerStart. Explainer: https://docs.google.com/document/d/1m3Mnuq7N9pLzFC8vu19ngxzUU1n3Lt_phzyK3u_UQ6M/edit?usp=sharing Bug: 1128786 Change-Id: I9e2277d546b07dff99341b8fa37f2b71139c8392 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413651 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#809740}
Showing
Please register or sign in to comment