All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=734568

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9vrdiQoM


Bot(s) for this bug's original alert(s):

chromium-rel-win7-dual

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976351658047894880

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976351041297875280

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : hans
  Commit : ba2ff9ad0d643a443575c839e56ae9edf7106643
  Date   : Mon Jun 05 02:02:06 2017
  Subject: Revert of "win: Set is_clang=true by default over the weekend."

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : image_decoding.image_decoding_measurement
  Metric       : ImageDecoding_avg/ImageDecoding_avg
  Change       : 20.37% | 84.5334333333 -> 101.748958333

Revision             Result                  N
chromium@476914      84.5334 +- 4.91511      6      good
chromium@476918      88.4213 +- 5.53301      6      good
chromium@476920      87.6324 +- 7.57647      6      good
chromium@476921      104.531 +- 9.91572      6      bad       <--
chromium@476927      105.008 +- 3.77607      6      bad
chromium@476940      101.749 +- 5.02349      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 image_decoding.image_decoding_measurement

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976351041297875280

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5640510871437312


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : khushalsagar
  Commit : 4e1be6ae8914f0eeed1df004b74a467bcb93241b
  Date   : Wed May 31 21:45:49 2017
  Subject: cc: Enable perf testing for checker-imaging.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : image_decoding.image_decoding_measurement
  Metric       : ImageDecoding_avg/ImageDecoding_avg
  Change       : 42.31% | 60.8601333333 -> 86.6118166667

Revision             Result                   N
chromium@475944      60.8601 +- 1.00307       6      good
chromium@476037      60.8071 +- 0.616818      6      good
chromium@476040      60.866 +- 0.453673       6      good
chromium@476041      84.194 +- 6.31997        6      bad       <--
chromium@476042      88.536 +- 7.05759        6      bad
chromium@476043      87.9802 +- 4.84668       6      bad
chromium@476049      87.2272 +- 7.69991       6      bad
chromium@476061      88.0405 +- 5.98309       6      bad
chromium@476084      86.481 +- 6.49016        6      bad
chromium@476130      86.6118 +- 6.64464       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 image_decoding.image_decoding_measurement

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976351658047894880

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5333802341105664


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!