=== Auto-CCing suspected CL author robhogan@gmail.com ===
Hi robhogan@gmail.com, 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 : Robert Hogan
Commit : 6abc19e88235609c7b8fc9df464beed2b667a773
Date : Sun Oct 08 22:09:22 2017
Subject: Opt to display the broken image icon where the spec allows it
Bisect Details
Configuration: mac_10_12_mini_8gb_perf_bisect
Benchmark : rasterize_and_record_micro.top_25
Metric : record_time/file___static_top_25_googleimagesearch.html
Change : 79.83% | 0.1 -> 0.179833333333
Revision Result N
chromium@507308 0.1 +- 0.002 6 good
chromium@507309 0.180333 +- 0.0033665 6 bad <--
chromium@507310 0.180167 +- 0.000912871 6 bad
chromium@507311 0.180167 +- 0.00168325 6 bad
chromium@507314 0.180167 +- 0.00168325 6 bad
chromium@507319 0.179833 +- 0.00168325 6 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=file...static.top.25.googleimagesearch.html rasterize_and_record_micro.top_25
More information on addressing performance regressions:
http://g.co/ChromePerformanceRegressions
Debug information about this bisect:
https://chromeperf.appspot.com/buildbucket_job_status/8966097976618409312
For feedback, file a bug with component Speed>Bisection
Transferring these to vmpstr@ as owner of the involved benchmark.
Note that the r_and_r benchmark is in consideration to be replaced (for perf regression monitoring purposes at least) by an updated repaint benchmark. More on that at issue 770800.
They are all static pages but many are missing some static images. We had a patch that fixed most all of those, but it hit the issue Ned mentions above. If we fix that, we could re-snapshot. This was the revert https://chromium-review.googlesource.com/c/chromium/src/+/769368
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 10 2017