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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/browse_news/browse_news_cnn

Revision             Result                  N
chromium@494141      1107.25 +- 1272.14      21      good
chromium@495501      1121.25 +- 1260.54      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.news.cnn 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/8970461101659513648


For feedback, file a bug with component Speed>Bisection

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

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

Graph jumps over 3 data points, bisecting on wider range.

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/browse_news/browse_news_cnn

Revision             Result                 N
chromium@494045      1104.5 +- 1446.75      21      good
chromium@495647      1111.7 +- 1107.43      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.news.cnn 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/8967809881836478128


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstPaint_avg/browse_news/browse_news_cnn

Revision             Result                  N
chromium@494045      1116.94 +- 1262.77      21      good
chromium@495647      1129.28 +- 1221.65      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.news.cnn 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/8967809855654678960


For feedback, file a bug with component Speed>Bisection

Not sure I correctly understand the result, but "1116.94 +- 1262.77" sounds like curious. Noise looks too large to be useful.

Some of these came back down, and all seem too noisy to bisect.