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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.ebay.com

Revision             Result                  N
chromium@492303      940.494 +- 36.1332      21      good
chromium@492345      942.592 +- 63.3434      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=http...www.ebay.com page_cycler_v2.basic_oopif

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

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


For feedback, file a bug with component Speed>Bisection

This benchmark was removed.