API regression |
|||
Issue descriptionGraphs: https://chromeperf.appspot.com/report?sid=d590c88ca7c97d76142472e6552d618fb1869e6755f8454bd8a34c26933324b9&start_rev=540468&end_rev=546338 Speedometer and google maps.
,
Mar 28 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14cb8007440000
,
Mar 28 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14cb8007440000 Get navigation info without using FrameLoader snapshots by dproy@chromium.org https://chromium.googlesource.com/catapult/+/5d35a2c7122c1ac4a9a37e7743a19f628f25a38b Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 29 2018
From what I understand, for the previous few builds, TTI was not being detected, and therefore only slices upto DOMContentLoaded [1] was counted in API:duration. After that change, TTI was detected again, slices upto TTI were counted, and it was obviously a bigger range and thus had bigger duration. Marking as WontFix. Reopen if you believe otherwise. [1]" https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/v8/runtime_stats_metric.html?l=157&rcl=9e3d4c4b70e0407995dc013e1cd8a92892f18c22 |
|||
►
Sign in to add a comment |
|||
Comment 1 by cbruni@chromium.org
, Mar 28 2018