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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : load:energy_sum/browse_search/browse_search_google

Revision             Result                  N
chromium@486750      103.485 +- 17.459       21      good
chromium@486845      104.603 +- 24.2302      20      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=browse.search.google 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/8973807273293521552


For feedback, file a bug with component Speed>Bisection

Looking at the graphs, it's clear that the ref builders are also regressing, so this is infra or a change that affects both.