Meausre LoadTime/SaveTime of CriticalPersistedTabData/TabState
Currently the load time we have includes the time taken on the sequenced task runner. Since CriticalPersistedTabData and TabState operations are both performed on the sequenced task runner, we block CriticalPersistedTabData read over the TabState read. This unfairly biases the CriticalPersistedTabData load time metric making it larger than it should be. It is better to compare the two independent of the sequenced task runner. Bug: 1166787 Change-Id: Ibc716f66cf9ec745d741f471bbd372048ef9edb9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627730Reviewed-by:Brian White <bcwhite@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: David Maunder <davidjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#844140}
Showing
Please register or sign in to comment