Add UMA tracking for post-paint "commit" time. |
|||||||
Issue descriptionIt looks like we don't have the right UMA stat(s) to track the overall paint time improvement from cc rtree patch http://crrev.com/2225563002/. We see the improvement in perf benchmarks: https://chromeperf.appspot.com/report?sid=f9bd827eff3a3ccc4817b231e58d32139a71bce3a463ccdfef035aae8766566d&start_rev=398691&end_rev=415291 but the Blink.Paint.UpdateTime UMA, for example, does not incorporate the time to append to cc's display item list and finalize. Discussion ensued re: adding new UMA to capture this. chrishtr@ noted that PictureLayer::Update trace macro may cover what we want, but is not UMA-ified.
,
Aug 31 2016
,
Aug 31 2016
,
Aug 31 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 31 2017
Is this still relevant? If we go with SPv1.75 is this irrelevant?
,
Aug 31 2017
Yes this is still relevant. The commit has significant cost.
,
Aug 31
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 31
Still need to look into this, but I will probably pick it up. Leaving it available til then. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajuma@chromium.org
, Aug 30 2016