Issue metadata
Sign in to add a comment
|
3.3%-34.1% improvement in system_health.memory_desktop at 537176:537506 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 16 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12b40151440000
,
Mar 16 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15aa5831440000
,
Mar 16 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12b40151440000 [SPv175] Enable SlimmingPaintV175 by default by wangxianzhu@chromium.org https://chromium.googlesource.com/chromium/src/+/0a9a5c311a1d3a298f952e495510bd6fe3faa2f6 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 16 2018
,
Mar 16 2018
Why is improvement a regression?
,
Mar 16 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/15aa5831440000 [SPv175] Enable SlimmingPaintV175 by default by wangxianzhu@chromium.org https://chromium.googlesource.com/chromium/src/+/0a9a5c311a1d3a298f952e495510bd6fe3faa2f6 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 16 2018
sullivan@, is memory improvement reported as regression bug intentional?
,
Mar 16 2018
wangxianzhu: any chromium committer can file a bug on an improvement to bisect it, but only regressions are part of the sheriffing workflow. hablich, can you clarify why you filed this bug?
,
Mar 21 2018
I wanted to find out where the improvement is coming from. Simple as that ;-).
,
Mar 21 2018
It's great to know our new feature has progressions. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 6 2018