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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                  N
chromium@490686      2800.05 +- 6890.25      21      good
chromium@490695      2416.08 +- 4262.15      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=browse.media.flickr.infinite.scroll system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Bisect can't repro and this is a noisy graph.