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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=8a9b64d9515f1e28884a69cdd6e7c8d458225d383e32958c38aac7181d8412e2


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstPaint_avg/load_search/load_search_amazon

Revision             Result                  N
chromium@490816      221.593 +- 114.168      21      good
chromium@490851      227.845 +- 131.906      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=load.search.amazon system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970462213114882240


For feedback, file a bug with component Speed>Bisection

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

Bisecting over a wider range.

=== Auto-CCing suspected CL author xunjieli@chromium.org ===

Hi xunjieli@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 : Helen Li
  Commit : 05ee1dbfaf0aa7c03b9ea2040f0345277042d0f1
  Date   : Mon Jul 31 13:24:01 2017
  Subject: [wpr-go] Switch system_health_desktop.json to use go

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/load_search/load_search_amazon
  Change       : 42.83% | 152.594333327 -> 216.319499999

Revision             Result                  N
chromium@490692      152.594 +- 36.8828      9      good
chromium@490725      150.853 +- 9.57095      6      good
chromium@490741      146.649 +- 9.24032      6      good
chromium@490749      149.817 +- 36.5821      9      good
chromium@490750      147.324 +- 12.3971      6      good
chromium@490751      231.551 +- 138.736      6      bad       <--
chromium@490753      240.766 +- 195.002      6      bad
chromium@490757      209.088 +- 94.3974      6      bad
chromium@490822      234.175 +- 110.006      6      bad
chromium@490952      245.171 +- 126.317      6      bad
chromium@491210      231.715 +- 101.372      6      bad
chromium@491727      192.808 +- 117.555      8      bad
chromium@492761      233.899 +- 153.394      9      bad
chromium@494830      216.319 +- 65.6753      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=load.search.amazon system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8967810007198869328


For feedback, file a bug with component Speed>Bisection