Issue metadata
Sign in to add a comment
|
A zero-to-nonzero regression in rendering.mobile at 580084:580278 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12cd3f94640000
,
Aug 9
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12cd3f94640000
,
Aug 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14cdc028640000
,
Aug 9
In the bisect, the last good revision showed a bad result. I started another bisect against an older revision range that should show good results. It they show bad results, this may depend on running environment, and is not a real regression.
,
Aug 9
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14cdc028640000
,
Aug 9
ok, they show good results... let me try another bisect :/
,
Aug 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1182e464640000
,
Aug 12
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1182e464640000 Enable use-zoom-for-dsf on Android on M70 by eirage@chromium.org https://chromium.googlesource.com/chromium/src/+/d0b8bbd2dbf9c06dcbbd01a4b1285cf7a1bc2ba0 0.01604 → 1.506 (+1.49) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 15
There is no significant difference between disable/enable --use-zoom-for-dsf for thread_raster_cpu_time_per_frame on the text_hover test. My change isn't the cause of this regression. Attach a local run result of text_hover_60000_pixels_per_second_desktop_gpu_raster. Left is with flag disable, same as without my change), right is with flag enable (with my change). Enabling the flag didn't cause the value to go up but down a little bit. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 9