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

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


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

chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@495808      1091.25 +- 51.237       21      good
chromium@495819      1098.79 +- 49.4723      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

not reproducible