=== BISECT JOB RESULTS ===
NO Perf regression found
Bisect Details
Configuration: mac_retina_perf_bisect
Benchmark : battor.trivial_pages
Metric : story:power_avg/TrivialGifPageSharedPageState
Revision Result N
chromium@485918 10.7357 +- 0.519842 21 good
chromium@486084 10.7304 +- 0.317148 21 bad
To Run This Test
src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=TrivialGifPageSharedPageState battor.trivial_pages
More information on addressing performance regressions:
http://g.co/ChromePerformanceRegressions
Debug information about this bisect:
https://chromeperf.appspot.com/buildbucket_job_status/8973437108912814784
For feedback, file a bug with component Speed>Bisection
=== Auto-CCing suspected CL author pdr@chromium.org ===
Hi pdr@chromium.org, the bisect results pointed to your CL, please take a look at the
results.
=== BISECT JOB RESULTS ===
Perf regression found with culprit
Suspected Commit
Author : pdr
Commit : 2b21ab04f7543ad0a20e02a92c60400b4e8e7f68
Date : Thu Jul 13 01:18:19 2017
Subject: Remove ImageQualityController
Bisect Details
Configuration: mac_retina_perf_bisect
Benchmark : battor.trivial_pages
Metric : story:power_avg/TrivialGifPageSharedPageState
Change : 6.99% | 6.90013488661 -> 7.31799308137
Revision Result N
chromium@485918 6.90013 +- 0.843558 9 good
chromium@486121 6.88346 +- 0.876833 14 good
chromium@486172 6.8593 +- 0.607361 9 good
chromium@486185 6.80199 +- 0.0592215 6 good
chromium@486191 6.85915 +- 0.393845 6 good
chromium@486194 6.81329 +- 0.114062 6 good
chromium@486196 6.81154 +- 0.076515 6 good
chromium@486197 7.35235 +- 0.0783865 9 bad <--
chromium@486222 7.34039 +- 0.0982873 9 bad
chromium@486323 7.31799 +- 0.110177 9 bad
To Run This Test
src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=TrivialGifPageSharedPageState battor.trivial_pages
More information on addressing performance regressions:
http://g.co/ChromePerformanceRegressions
Debug information about this bisect:
https://chromeperf.appspot.com/buildbucket_job_status/8973182926192212800
For feedback, file a bug with component Speed>Bisection
I am not able to reproduce this on my retina mac locally (without battor) but I think I see why we regressed. This testcase has a huge animated gif and the ImageQualityController patch changed the filter quality from high to medium. This shouldn't have an effect but I suspect a bug further down the pipeline.
I'm going to put up a patch that restores the medium quality for animated images and see if that fixes the regression.
This bug requires manual review: M61 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Before we approve merge to M61, please answer followings:
* Is this M61 regression? Is it critical?
* Is the change well baked/verified in Canary, having enough automation tests coverage and safe to merge to M61?
* Any other important details to justify the merge.
Please note M61 is already in Beta, so merge bar is very high. Thank you.
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 21 2017