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

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


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

chromium-rel-win7-dual
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : trace_import_duration_avg/http___www.amazon.com

Revision             Result                  N
chromium@490927      2824.51 +- 4656.15      21      good
chromium@491274      3309.91 +- 6230.46      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.amazon.com tracing.tracing_with_debug_overhead

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

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


For feedback, file a bug with component Speed>Bisection

This benchmark has been turned down.