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

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


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

android-nexus5
android-nexus7v2
android-webview-nexus5X
chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_chrome/load_chrome_blank

Revision             Result                      N
chromium@510723      0.0646137 +- 0.0405315      21      good
chromium@510764      0.0645035 +- 0.0293279      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank 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/8964802179061391840


For feedback, file a bug with component Speed>Bisection