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

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


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

chromium-rel-mac11
chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/cold/Taobao

Revision             Result                  N
chromium@512468      1335.58 +- 1120.19      21      good
chromium@513098      1406.6 +- 1019.86       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=Taobao loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Most recovered.  The rest are too noisy to be bisectable.