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

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


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

chromium-rel-win7-gpu-intel

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

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

Suspected Commit
  Author : Takashi Toyoshima
  Commit : 36160f0427ad5657e299fa932c920d1f490bc1e1
  Date   : Mon Oct 16 10:23:14 2017
  Subject: ResourceLoadScheduler: update fieldtrial_testing_config.json

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.owp_storage
  Metric       : blob-build-all-then-read-serially/blob-build-all-then-read-serially
  Change       : 1.89% | 123.422166667 -> 125.76075

Revision             Result                  N
chromium@508991      123.422 +- 3.03412      9      good
chromium@509008      122.911 +- 1.7573       6      good
chromium@509009      126.53 +- 2.33927       6      bad       <--
chromium@509010      126.717 +- 2.11834      6      bad
chromium@509012      126.008 +- 3.66157      6      bad
chromium@509016      126.48 +- 1.98123       6      bad
chromium@509024      125.761 +- 2.72978      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.owp_storage

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

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


For feedback, file a bug with component Speed>Bisection